Re: WebExtensions changes coming?
Posted: Thu Nov 14, 2019 1:45 pm
NoScripters and WebSec nerds of all lands, unite!
https://forums.informaction.com/
https://blog.nightly.mozilla.org/2022/0 ... issue-124/WebExtension Manifest Version 3 support has been enabled by default in Nightly and Early Beta builds (starting from Firefox 106) – Bug 1789796
This change will allow developers to start testing “manifest_version: 3” extensions without flipping a pref (by installing temporarily or permanently with signing checks disabled)
Again, a reminder that Mozilla plans to continue support for the Manifest v2 blocking WebRequest API (this API powers, for example, uBlock Origin) while simultaneously supporting Manifest v3.
Have a Manifest v2 WebExtension that you want to migrate? Here’s our migration guide!
I have some extensions that use contentScripts.register() with string code so that dynamically-set variables can be passed to a content script that's reliably run at document-start before any page script can run. What is the (Firefox) Manifest V3 way to achieve this?https://extensionworkshop.com/documentation/develop/manifest-v3-migration-guide/ wrote:The new Scripting API takes over the features of tabs.insertCSS(), tabs.removeCSS(), and tabs.executeScript() and adds capabilities to register, update, and unregister content scripts at runtime.
Also, the code parameter is removed so that arbitrary strings can no longer be executed. This API requires the scripting permission. So, you need to move any arbitrary strings executed as scripts to files and rewrite your code to use the Scripting API.
https://blog.mozilla.org/addons/2022/11/17/manifest-v3-signing-available-november-21-on-firefox-nightly/ wrote: To be clear, Firefox will continue to support MV2 extensions for the foreseeable future, even as we welcome MV3 extensions in the release to general availability in Firefox 109 (January 17, 2023). Our goal has been to ensure a seamless transition from MV2 to MV3 for extension developers.
[...]
Towards the end of 2023 — once we’ve had time to evaluate and assess MV3’s rollout (including identifying important MV2 use cases that will persist into MV3) — we’ll decide on an appropriate timeframe to deprecate MV2. Once this timeframe is established, we’ll communicate MV2’s closure process with advance notice.
bump.barbaz wrote: ↑Thu Sep 22, 2022 3:43 pm I have some extensions that use contentScripts.register() with string code so that dynamically-set variables can be passed to a content script that's reliably run at document-start before any page script can run. What is the (Firefox) Manifest V3 way to achieve this?
And from that "previous MV3 update" link, also from 2024:https://blog.mozilla.org/addons/2024/05/14/manifest-v3-updates/ wrote: We also wanted to take this opportunity to address a couple common questions we’ve been seeing in the community, specifically around the webRequest API and MV2:
- The webRequest API is not on a deprecation path in Firefox
- Mozilla has no current plans to deprecate MV2 as mentioned in our previous MV3 update
https://blog.mozilla.org/addons/2024/03/13/manifest-v3-manifest-v2-march-2024-update/ wrote: We continue to support DOM-based background scripts in the form of Event pages, and the blocking webRequest feature, as explained in our previous blog post. Chrome’s version of MV3 requires service worker-based background scripts, which we do not support yet. However, an extension can specify both and have it work in Chrome 121+ and Firefox 121+. Support for Event pages, along with support for blocking webRequest, is a divergence from Chrome that enables use cases that are not covered by Chrome’s MV3 implementation.
Well what’s happening with MV2 you ask? Great question – in case you missed it, Google announced late last year their plans to resume their MV2 deprecation schedule. Firefox, however, has no plans to deprecate MV2 and will continue to support MV2 extensions for the foreseeable future.