Reality: Firefox does something differently and you’ll run into CORS issues. Misconception 3:Ī simple fetch will behave the same in Chrome and Firefox. Even small differences like and behaving differently. Reality: There’s subtle differences so you’ll still end up with either platform conditions or separate code bases. The Web Extension shares the same code for all platforms. For now Firefox doesn’t really support Manifest 3, their extension testing website is only working with v2 ( or at least is broken in general) and all the tooling to build a Safari extension is only working for Manifest v2. Reality: Mozilla and Google are still fighting over what Manifest v3 is supposed to be. Manifest 3 is the new hotness and that’s what you should use “Write once, run anywhere” was once again a lie. I found out that it was optimistic to think that now you’ll write one extension, compile it for the 3 platforms, upload it to the respective extension stores and you are done. I was hesitant to build one as the development experience of doing everything in the browser seemed annoying to debug.Īfter hearing more and more about Web Extensions and even Safari adding support recently I assumed that now is the time to take this on. For my new side project I needed to build a browser extension.
0 kommentar(er)
