3 ms·
My company's main products are browser extensions. At first, our Chrome extension was the most popular, but I anticipate with the upcoming changes we may say go
by gnicholas 5y ago
My company's main products are browser extensions. At first, our Chrome extension was the most popular, but I anticipate with the upcoming changes we may say goodbye to Chrome and just be on Firefox and Safari, depending on how they deal with V3 issue. We simply don't make enough money from our Chrome extension to deal with all of their big changes. Last year they ditched the Webstore Payments, last summer they migrated Google Docs (one of our most popular use cases) from DOM to canvas-based rendering, and now this. We can't keep rewriting major parts of our codebase at the whim of big G.
- MaknMoreGtnLess 5y ago> My company's main products are browser extensions How well does the "WebExtensions API cross-browser technology" [0] work to build ONE code base and have to work well across Google Chrome, Firefox or even Safari? [0] https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/Web...
- gnicholas 5y agoIt has worked well for the last several years when we could easily deploy changes to Chrome and Firefox. I have no idea what we’re going to do with the upcoming manifest schism. Safari is just mobile for us, though if Chrome goes through with V3 we may offer safari for desktop also.
- MaknMoreGtnLess 5y ago> I have no idea what we’re going to do with the upcoming manifest schism OK - is this issue then that the upcoming Chrome manifest changes break Chrome's compatibility with the standard or these were features that were never part of the standard to begin with and very specific to Chrome?
- gnicholas 5y agoFrom talking with my dev, my understanding is this has to do with scripts and service workers. I believe these were not specific to Chrome previously, but I'm not sure.