3 ms·
I'm in a similar boat, wrote a MV2 plugin for firefox, started looking at MV3 got confused about which bits are going to be usable and which are not and when. E
by joshka 4y ago
I'm in a similar boat, wrote a MV2 plugin for firefox, started looking at MV3 got confused about which bits are going to be usable and which are not and when. Ends up being too difficult.
From a extension creator perspective, it might be better to just pull all mention of MV3 on the MV2 pages until it's properly baked.
- vdfs 4y agoFYI Firefox is ditching MV2 too, they are keeping web request blocking but they will deprecate v2
- joshka 4y agoYeah, it's in the nightly and going to GA Jan 23 according to the latest blog post on it.
- Vinnl 4y ago> MV2 will continue to work. We have not made decisions about MV2 deprecation yet. We want to see what the response and adoption of MV3 is from the community next year and will then make decisions about the future based on that. https://blog.mozilla.org/addons/2022/10/31/begin-your-mv3-migration-by-implementing-new-features-today/#comment-227534 https://blog.mozilla.org/addons/2022/10/31/begin-your-mv3-mi...
- vdfs 4y agohttps://blog.mozilla.org/addons/2022/05/18/manifest-v3-in-firefox-recap-next-steps/ https://blog.mozilla.org/addons/2022/05/18/manifest-v3-in-fi... I guess they are following Chrome migration plan by delaying the inevitable
- Vinnl 4y agoI don't think that says anything about concrete plans for ditching MV2 yet?