2

These are a great feature; and a perfect way to sidestep the weight (and security issues) of having a ton of tiny single-purpose browser-extensions from authors that you don't know.

However, at the moment, it appears that they don't have a lot of the power of browser-extensions - for instance, I tried to copy the meat of this simple "Popout Tab" extension into a programmable button; but it appears they don't have access to the WebExt APIs:

ReferenceError: Can't find variable: browser

This would obviate any need for a variety of small extensions, especially those that are only occasionally useful, and are only useful on-trigger. They lend themselves well to small snippets of code that don't need updating, and that also makes them relatively secure.

    It's possible too, but we will want to keep both separate, as this will introduce a big security concern.
    We can introduce some safe internal APIs for Programmable Buttons in future for better handling instead of web-ext APIs 💪

      No one is typing