Re:Mozilla reaffirms that Firefox will continue to support c...
by anvic on Saturday September 24, 2022 @07:37AM
(#32961580)
I read somewhere that even though Mozilla will continue supporting the ad blocking API from manifest v2, the rest of manifest v2 will be completely dropped so most of the extensions that I use like greasemonkey will stop working. Is that true?
[ Parent
| on HN ]
Re:Mozilla reaffirms that Firefox will continue to support c...
by tyingq on Saturday September 24, 2022 @08:15AM
(#32961804)
There's a migration guide here: https://extensionworkshop.com/documentation/develop/manifest...
Since they aren't taking away the onBeforeRequest() functionality, I don't see a good reason why greasemonkey can't be ported over.
Re:Mozilla reaffirms that Firefox will continue to support c...
by anvic on Saturday September 24, 2022 @08:19AM
(#32961824)
Under "Scripting API" it says "the code parameter is removed so that arbitrary strings can no longer be executed [...] you need to move any arbitrary strings executed as scripts to files". I don't see how something like greasemonkey can continue existing given that limitation.
Re:Mozilla reaffirms that Firefox will continue to support c...
by tyingq on Saturday September 24, 2022 @08:57AM
(#32962138)
Ah, yeah, that does look like a gap. Tampermonkey's related issue, though it seems to be mostly focused on Chrome: https://github.com/Tampermonkey/tampermonkey/issues/644
Re:Mozilla reaffirms that Firefox will continue to support c...
by lapcat on Saturday September 24, 2022 @10:00AM
(#32962689)
This is because Firefox is adding Manifest v3 support without dropping v2 support, unlike Chrome.
Re:Mozilla reaffirms that Firefox will continue to support c...
by coldpie on Saturday September 24, 2022 @08:45AM
(#32962016)
Googling "tampermonkey manifest v3" lead me to this issue, which has a lot of relevant discussion: https://github.com/Tampermonkey/tampermonkey/issues/644