-
This add-on needs to be rewritten to use WebExtensions in order to be compatible with Firefox 57+.
I've been looking at the WebExtensions APIs, and there is an [`onBeforeSendHeaders`](https://devel…
-
NoScript has recently introduced a [patch](https://github.com/hackademix/noscript/commit/f5cf60b4a9d467ebb8f80ced67e87602df33cef4) to modify all `[loading="lazy"]` attributes to `[loading="eager"]` wh…
-
This is a very useful extension, so I would hate to see its demise in later Firefox versions. Is it possible to re-implement the extension with the WebExtension API? It won't be able to reside in the …
-
I don't know if you know, but Firefox is planning to standardize their addons to match Webkit by introducing a new [WebExtensions API](https://blog.mozilla.org/addons/2015/08/21/the-future-of-developi…
-
It is used to transfer links & cookies from browser, since WebExtension is used in both Firefox & Chrome.
API docs:
https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Native_messaging
-
Will this extension be compatible with the new Webextension APIs / Firefox 57?
-
**Describe the bug**
When pressing the save now button I get an error saying "you need to be logged in", but I am logged in (can confirm it by pressing the "my archive" button. It also doesn't seem t…
-
The following APIs are implementation specific and need our own version:
- [ ] #21
- [ ] #20
- [ ] #22
- [ ] #23
- [ ] #24
- [ ] #25
- [ ] #26
- [ ] Inspect Window
- [ ] Network
-…
-
### What type of issue is this?
Incorrect support data (example: BrowserX says "86" but support was added in "40")
### What information was incorrect, unhelpful, or incomplete?
Compatibility chart …
-
**The issue**
Google/Chrome, Mozilla/Firefox and Apple/Safari all allow MV3 webextensions defining both `background.service_worker` and `background.script` in the manifest. In such cases browser wi…