This also opens it up to different Touch Bar input types (popover, groups, video controls…) in the future. The idea here is that in the future if/when this is opened up to an API, XUL actions could be defined when the Touch Bar inputs are created. For example, there could be a “.button.View:FullScreen” or a “.popover.cmd_find”. Now, the identifiers of Touch Bar inputs are a string consisting of both their type and their action. Originally, actions were stored as NS_STRINGs in an array, and then each Touch Bar button had an index into that array.
#Firefox for mac touch bar code#
I’ve made some changes to Erica’s code, but hit a weird bug.Īs for the changes, the code is functionally almost the same, but it handles how actions are performed a little differently. A "control strip" of extension buttons could be there for activating favorite extensions - used just like the space in the standard tool bars at the top of the browser window, but on a global basis. Stats and performance data could be shown there in real time reflecting the current browser context. Imagine an API that lets extensions add various types of controls or even a Canvas with its touch events to the Touch Bar, thereby making this an offscreen but still user-visible and interactable area for extensions to present information and interact with users.ĭev Tools could be presented there. I use them all the time but not quite all the time enough to want to lose that screen space.īut the idea I'm most excited about: We could use create a DOM window mapped to the Touch Bar's graphics context, so that you could then draw Web content into the Touch Bar from a WebExtension.
I'd love to, for instance, have the dev tools toolbar always displayed there. There's a lot of neat stuff we could do with the Touch Bar. Chrome has the same problem with text fields in websites. When focus is in the URL bar, you get icons of the URL bar dropdown items. When a text field is focused, you get the usual word suggestions. When a video is playing, Safari lets you control playback and scrub through the video from the touch bar. Through "View -> Customize Touch Bar." you can add more buttons, e.g.
#Firefox for mac touch bar update#
When more than one tab is open, they show previews of tab contents (which don't update live or even on tab switch maybe only once on pageload even). Safari by default shows Back/forward, a very wide button that looks like their empty URL bar (search icon + the text "Search or enter website name") which just focuses the URL bar when tapped, and a new tab button. With XCode 8.1 and a version of 10.12.1 that is linked to at the bottom of, you can put a touch bar on your screen to test what other apps are doing.
0 kommentar(er)
