You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While extensions such as Vimium-FF and Saka Key make do only with
what's provided to regular WebExtensions, prior art in Vimium demonstrates
limitations. These include loss of functionality on protected pages
requiring non-Vimium motions to navigate away from and Vimium needing to implement its own
location and findbar. In tandem with Colin Caine's Keyboard API, this API
landing means a user can define their own motions for Firefox's shortcuts and be usable
anywhere they normally are. It is our hope this use will go a long way in
Vimperator or Pentadactyl successors.
Ensure extensions.legacy.enabled is set to "carview.php?tsp=true" in about:config (an Experiment is
really a legacy extension).
Enter about:debugging and load keyboard-shortcut-api/schema.json to load the API.
Load /test-extension/manifest.json to load our test extension that adds a browser
action (i.e., a button on your toolbar) which opens a sample page that calls the functions
our API returns.
Considerations for reviewers
Currently, the implementation to toggle caret browsing with F7 is hardcoded inside
source/toolkit/content/widgets/browser.xml. Is there any intent to encapsulate this? If
not, is the verbatim reuse in the API acceptable?
If at all, how would you like tests to work?
As of September 24 2017, we notice that gDevToolsBrowser contains a function
onKeyShortcut() that is not exposed. Our API could be made more concise using this call.
Related, gDevToolsBrowser.getDeveloperToolbar() seems to be the best way to get the
developer toolbar but is also not exposed. We currently have no implementation to toggle
the toolbar.
Though not shortcuts, we've implemented functions that check if the current page is in
fullscreen, reader mode or in caret browsing.
If we can manage, we intend to implement a new shortcut here that focuses tab content,
escaping from browser chrome. Do we have approval for this? A tentative implementation has
been added, but hasn't been determined to be robust.
About
A webextension experiment that aliases commands for native keyboard shortcuts.