-
_(living summary: updated @ 2018-09)_
This issue tracks browser extension support for various protocol schemes and URIs according to [four stages of the upgrade path for path addressing](https://gi…
lidel updated
2 months ago
-
Love the addon, and I'd like to help make it e10s compatible. Would you be open to a PR that addresses that?
-
This is a tracking issue for building the next version using WebExtensions for Firefox 48+ (their targeted release window). WebExtensions almost has all the features we need, but we'd need two serious…
-
### What information was incorrect, unhelpful, or incomplete?
saved
https://github.com/mdn/webextensions-examples/tree/main/favourite-colour
### What did you expect to see?
saved
### Do you…
-
### Summary
The `AddonsSidebar` macro does not behave as expected when viewing WebExtensions JavaScript API documentation. When visiting an API namespace page, the "JavaScript APIs" section in the le…
-
Hi! This is a great tool but I'm struggling to make it useful. Graphs are not a great way to represent dependencies because shared dependencies are pulled so far right and away from their importers, f…
-
# Short Summary
Pack Webextension to make it ready for shipping.
# Explanation
To make the Webextension installable as something other than a "temporary extension", it needs to be packed and …
-
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…
-
I followed the compilation steps and when loading the zip-file FF says, the extension seems to be damaged.
Reading manifest: Warning processing version_name: An unexpected property was found in the W…
immwi updated
3 weeks ago