Firefox unsupported background script

Turns out that Firefox officially supports Manifest V3, but not in the same way that Chromium supports it
One major way that they differ in is the background script: https://blog.mozilla.org/addons/2022/05/18/manifest-v3-in-firefox-recap-next-steps/#:~:text=privacy%20tools%20available.-,Event%20Pages,-Chrome%E2%80%99s%20version%20of
TL;DR

background.service_worker

background.service_worker

is not supported, so Firefox must be a special use-case in Plasmo

Mozilla Add-ons Community BlogRob Wu

Manifest v3 in Firefox: Recap & Next Steps

It’s been about a year since our last update regarding Manifest v3. A lot has changed since then, not least of which has been the ...

lab•1/31/23, 1:40 AM

oh lol

lab•1/31/23, 1:40 AM

man what a pain in the butt eh xd....

lab•1/31/23, 1:40 AM

Thanks for the heads up, we can def add it to the special handling when generating the manifest

lab•1/31/23, 1:40 AM

Tho...

lab•1/31/23, 1:41 AM

this requires a slight change to the manifest schema

lab•1/31/23, 1:45 AM

and damn that post been around since May 2022

AviOP•2/1/23, 4:56 PM

I think I will only make my extensions MV3 on Firefox when porting to Plasmo lol
Can't be bothered to learn about Event Pages shit

lab•2/1/23, 4:57 PM

lol yeah

lab•2/1/23, 4:57 PM

idk why they keep trying to divert

AviOP•2/1/23, 4:58 PM

I don't think they're "trying to divert"
More like, "Google hasn't done a great job with MV3, we don't want to repeat their mistakes"

lab•2/1/23, 5:00 PM

I mean they can just fork the service worker runtime on chrome and make it better, then just use the same structure

lab•2/1/23, 5:00 PM

no need to add 3 whole new APIs

AviOP•2/1/23, 5:04 PM

I have a friend who's an ext dev, and since he first learned about SW, he complained non-stop about it and just swallowed the pill
He tried to convince Google ext dev employees that it needs to change and stuff like that
I.e. Google's execution was so bad in his mind (and not just his) that Mozilla didn't want to be seen in the same light
Of course, the other side of the equation means that it's harder to develop cross-platform exts, but it might be easier to transition MV2 extensions to MV3 when it comes to Firefox, whereas on other browsers, if your extension heavily relied on the background page's availability, keeping up with MV3 means a complete architectural change

AviOP•2/1/23, 5:05 PM

E.g. my https://github.com/avi12/youtube-downloader will require a complete architectural change to make it compatible with Chromium's MV3