|
|
|
|
|
by falafelite
1590 days ago
|
|
Hi Simeon, I appreciate your engagement on this. I suppose I am being dramatic in wording it as a "separate codebase", and yes, one can generate two separate manifest.json files. My end-result has been to have separate code for Chrome and Firefox, though, because the polyfill doesn't work as advertised and as you've noted, there are certain things that are not compatible across different browsers. It isn't a horrible workaround, but I will need to update code in two places every time I want to make a change, and that is bad developer experience, bad for timely updates, bad for being able to support a user regardless of the browser they use. I don't care what they use, I just want them to be able to use my tool. But as far as I can tell, the whole ecosystem for developing and publishing browser extensions is quite behind, at least as compared to the rest of the things I work on. I appreciate your general guidance, and accept that this simply isn't the best state of things to work with. |
|