A number of extension developers have reached out to ask how Mozilla plans to respond to the changes proposed in Google’s update to their extensions API, commonly known as Manifest v3. We have answered some of the frequently asked questions on the Add-ons Blog , and we welcome feedback on this threa…

Remotely hosted code : Firefox already does not allow remote code as a policy. Manifest v3 includes a proposal for additional technical enforcement measures, which we are currently evaluating and intend to also enforce. Please do not do this. At best, users should have the ability to vet and appr…

Hi @mitozen , first of all, welcome to the Mozilla Discourse community. [image] mitozen: introducing this change will break Greasemonkey, Tampermonkey, and Violentmonkey, I think there is a misunderstanding here, as the extensions you name actually just got it’s own API , so they can inject us…

Rugkx is correct, this only refers to remote extension code, which is already disallowed on AMO. We recently added an API specifically to support safe usage of user scripts, we love and fully support them. [image] zephyr: Does such a roadmap exist? If not, would Mozilla please be willing to cr…

I use blocking webrequests to abort loading a page when a TLS certificate has changed and the author wants to authorize this first (TLS certificate pinning, see add on https://addons.mozilla.org/de/firefox/addon/certificate-pinner/) ). Removing the blocking webrequests API would render my add-on unus…

[image] zombie: Please file this, and any other specific use cases you may find, and make them block bug 1578286 so that we can track them New issue filed: 1580254 - Support CSS selector validation API from a service worker I do not have the power to modify the bug to mark it as blocking ht…

Thank you for taking the time to address the roadmap.

Firefox is my beloved browser for three main reasons: Privacy Customizability Independency Therefore, I hope changes to the extensions API do not take away any of the existing possibilities (no regression just because of compliance with Google’s Manifest or marginal security/performance improve…

[image] BelFox: add new possibilities instead (eagerly waiting for a Toolbar API :pray:) For the Toolbar API, you can follow bug 1215064 .

Please help me gather some thoughts to bring up at MozFest: [image] Collecting your thoughts about Manivest V3 and the Recommended Extensions program Development As the developer of a recommended extension ( forget me not ), I have been invited by Mozilla to join a full day…

[Blog post] Mozilla's Manifest v3 FAQ

Add-ons Announcements

zombie (Tomislav Jovanovic) September 10, 2019, 11:47pm 12

Thanks, you should have that power (editbugs) from now on.

Topic		Replies	Views
Migrating to Manifest v3 Development	12	7129	June 27, 2020
[Blog post] Manifest v3 update Announcements manifest-v3	6	4153	September 24, 2021
Impossible to upgrade to manifest v3 for extensions that require constant/persistent listeners Development	16	6985	January 9, 2024
Newer Manifest v3 Information? (Scope, timeline, etc.) Development	5	1777	October 8, 2021
[Blog post] Manifest v3 in Firefox: Recap & Next Steps Announcements manifest-v3	11	5772	June 14, 2024

[Blog post] Mozilla's Manifest v3 FAQ

Related topics