How can I change an add-on's _execute_browser_action command?
eric.promislow at gmail.com
Wed Oct 18 20:15:28 UTC 2017
Interesting. I imagine that a `commands.update` command might be easier to
implement than the full API page with nice UI. From reading
it looks like it's a matter of updating each browser window's keyset.
So what's involved in modifying the API? Obviously more than adding a field
to ext-commands.js and documenting it. I see the w3c is recognizing a Browser
Extension Community Group <https://www.w3.org/community/browserext/> . It
defines a core API (at https://browserext.github.io/browserext ), but
`commands` isn't in that list. So can Mozilla duly proceed to add an
On Tue, Oct 17, 2017 at 11:03 PM, Michael Buckley <support at codefisher.org>
> God Bless
> On 18/10/17 4:04 pm, Eric Promislow wrote:
> The only supported method in the commands API is 'getAll'.
> Chrome supports 'chrome://extensions/configureCommands' which lets the
> add-on user set each installed add-on's startup key.
> This doesn't look supported in Firefox. Is there a roadmap to either
> a commands.update method (signature: command name, object payload),
> or build a page like Chrome has?
> After being around for 8 years, Tabhunter users have expected to be able
> to set their preferred keyboard shortcut for launching it. Is there a
> alternative to crafting a custom manifest.json for each user?
> - Eric
> Dev-addons mailing listDev-addons at mozilla.orghttps://mail.mozilla.org/listinfo/dev-addons
> Dev-addons mailing list
> Dev-addons at mozilla.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Dev-addons