WebExtensions changes coming?

General discussion about web technology.
barbaz
Senior Member
Posts: 10401
Joined: Sat Aug 03, 2013 5:45 pm

Re: WebExtensions changes coming?

Post by barbaz » Thu Nov 14, 2019 1:45 pm

*Always* check the changelogs BEFORE updating that important software!
-

barbaz
Senior Member
Posts: 10401
Joined: Sat Aug 03, 2013 5:45 pm

Re: WebExtensions changes coming?

Post by barbaz » Thu Nov 12, 2020 3:03 pm

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".
*Always* check the changelogs BEFORE updating that important software!
-

barbaz
Senior Member
Posts: 10401
Joined: Sat Aug 03, 2013 5:45 pm

Re: WebExtensions changes coming?

Post by barbaz » Fri Sep 24, 2021 12:54 am

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?
*Always* check the changelogs BEFORE updating that important software!
-

User avatar
therube
Ambassador
Posts: 7808
Joined: Thu Mar 19, 2009 4:17 pm
Location: Maryland USA

Re: WebExtensions changes coming?

Post by therube » Fri Dec 10, 2021 6:51 pm

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


(FF, being the follower that it is, you know where it will end up...)
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball NoScript FlashGot AdblockPlus
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0 SeaMonkey/2.53.11

User avatar
therube
Ambassador
Posts: 7808
Joined: Thu Mar 19, 2009 4:17 pm
Location: Maryland USA

Re: WebExtensions changes coming?

Post by therube » Fri May 20, 2022 4:53 pm

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball NoScript FlashGot AdblockPlus
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0 SeaMonkey/2.53.13

barbaz
Senior Member
Posts: 10401
Joined: Sat Aug 03, 2013 5:45 pm

Re: WebExtensions changes coming?

Post by barbaz » Fri Sep 09, 2022 5:28 pm

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.
*Always* check the changelogs BEFORE updating that important software!
-

User avatar
therube
Ambassador
Posts: 7808
Joined: Thu Mar 19, 2009 4:17 pm
Location: Maryland USA

Re: WebExtensions changes coming?

Post by therube » Thu Sep 22, 2022 3:25 pm

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/
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball NoScript FlashGot AdblockPlus
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0 SeaMonkey/2.53.15

barbaz
Senior Member
Posts: 10401
Joined: Sat Aug 03, 2013 5:45 pm

Re: WebExtensions changes coming?

Post by barbaz » Thu Sep 22, 2022 3:43 pm

Thanks for the link therube.

From the mentioned migration guide -
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.
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?
*Always* check the changelogs BEFORE updating that important software!
-

Post Reply