2 ms·
Not yet, unfortunately, since Chrome broke compatibility with other browsers for new extensions. (Specifically: it now mandates "Manifest V3" for new extension
by Vinnl 4y ago
Not yet, unfortunately, since Chrome broke compatibility with other browsers for new extensions.
(Specifically: it now mandates "Manifest V3" for new extensions, which Firefox is still implementing (it basically has to follow what Chrome is doing, given Chrome's reach). Once Manifest V3 works on more browsers, I should be able to relatively easily upgrade, and then support Chrome as well.)
Edit: oh, I should probably also add that I'm a Mozilla employee, but this is a personal project, and I'd have done the same if I hadn't been.
- Raed667 4y agoFor an extension like this, I don't think you need to change much besides just putting "manifest_version": 3 in your manifest.json I don't see any breaking changes here.
- Vinnl 4y agoIt's compatibility with other browsers that would be broken; Firefox can't install extensions with "manifest_version": 3 in their manifest.json yet without a flag.
- Raed667 4y agoOh yes absolutely. I wasn't clear enough in my comment, I was suggesting you can make a branch in your project repository for chrome. Make the change only there until Firefox supports MV3.