-
> (this is placeholder issue, will be updated as we work on spec prototypes, discuss with vendors etc)
## Problem
Currently (2023Q3):
1. The web platform supports registering custom protocol…
lidel updated
5 months ago
-
## Problem
Extensions host permissions are not granular enough:
- if the extension requests "all sites" access (via manifest or `permissions.request()`), there's no way to remove specific websit…
-
It would be great if you could remove the Chrome-specific parts of this extension (where possible) to conform to the [WebExtensions](https://developer.mozilla.org/en-US/Add-ons/WebExtensions) standard…
-
There is a Chrome addon called that Comic Updater that works similarly to yours, but is less fully featured. (It doesn't prompt when running into collisions--it either just picks the one it things is …
-
Once Firefox 57 is out, CoLT as-is will stop working.
I'm assuming from #12 from 2014, that WebExtensions support is not in the works by @jgbishop, and so unless somebody else picks up the task, th…
-
This includes `chrome` and `browser` declared in the global namespace.
-
Right now it seems like trunk is rather website-focused, since it won't let me build my code without an `index.html` file.
Another thing that'd be awesome to see is a way to reference say `dist/ind…
-
MDN URL: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Native_messaging
#### What information was incorrect, unhelpful, or incomplete?
The nodejs example of the native app…
-
It's time.
-
Mozilla has plans to [remove non-WebExtensions addon](https://blog.mozilla.org/addons/2017/02/16/the-road-to-firefox-57-compatibility-milestones/) support with the release of Firefox 57 ([Developer Ed…