3 ms·
Glad to see Mozilla is holding up it's independence on this key issue, whereas Edge chose to implement Google's changes as-is.
by ocdtrekkie 5y ago
Glad to see Mozilla is holding up it's independence on this key issue, whereas Edge chose to implement Google's changes as-is.
- whymarrh 5y agoThere could be a simple explanation for this: Mozilla has its own browser stack whereas Edge is Chrome.
- seriousquestion 5y agoThat could be, it's just easier for Edge to follow Google.
- ocdtrekkie 5y agoThey went so far as to write a blog officially taking a position on the issue: https://blogs.windows.com/msedgedev/2020/10/14/extension-manifest-chromium-edge/ https://blogs.windows.com/msedgedev/2020/10/14/extension-man...
- freediver 5y agoAnother browser that you probably never heard of (Orion Browser) is also holding its independence on this key issue, keeping the support for webRequest API, and on top of WebKit no less. (disclaimer: founder)