WebExtensions changes coming?

[barbaz]

https://www.ghacks.net/2019/11/13/googl ... canary-80/

[barbaz]

Firefox will keep blocking webRequest in their Manifest v3 for now, implementing declarativeNetRequest as an additional API - https://www.youtube.com/watch?v=tpDFS-GUytg (7:16)

Though at 11:00, Rob says that "in the long term, we would like to encourage the use of declarative APIs and discourage blocking APIs if possible".

[barbaz]

Chrome will kill Manifest V2 in 2023 - https://developer.chrome.com/docs/exten ... v2-sunset/

Does Firefox have any clear plans to kill its Manifest V2?

[therube]

EFF: Chrome Users Beware: Manifest V3 is Deceitful and Threatening


(FF, being the follower that it is, you know where it will end up...)

[therube]

ghacks: Mozilla expects to launch extensions Manifest V3 support in Firefox in late 2022

[barbaz]

An experimental Manifest V3 content blocker by gorhill - https://chrome.google.com/webstore/deta ... hcphecmpfh
The description contains some interesting information about the impact of Manifest V3.

[therube]

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!

https://blog.nightly.mozilla.org/2022/0 ... issue-124/

[barbaz]

Thanks for the link therube.

From the mentioned migration guide -

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.

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?

[therube]

Just a matter of time, https://www.theregister.com/2022/11/17/ ... ill_begin/ signing Mv3 extensions for Firefox next week.

[barbaz]

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.

[barbaz]

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?

bump.

I did find scripting.executeScript's "func" parameter for one-off "later" injections of this type. But still can't find any API that can do similar reliably at document_start, i.e. run in a page definitely prior to any page's code?

(Seems the contentScripts API doesn't exist in Manifest v3, so guess that's not an option?)

[therube]

Google’s revised Chrome extension standard loosens restrictions on ad blockers

Loosing a noose will still kill the person with the noose around their neck.

[barbaz]

Recently happened on a couple Mozilla blog posts from last year that answer most of the open questions in this thread:

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:

1. The webRequest API is not on a deprecation path in Firefox
2. Mozilla has no current plans to deprecate MV2 as mentioned in our previous MV3 update

And from that "previous MV3 update" link, also from 2024:

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.