4 ms·
So this is is a MAJOR flaw with WebExtension design. Each uses a separate URI scheme. So Chrome uses chrome-extension: Firefox uses firefox-extension: ... e
by burtonator 6y ago
So this is is a MAJOR flaw with WebExtension design.
Each uses a separate URI scheme.
So Chrome uses chrome-extension:
Firefox uses firefox-extension:
... etc.
which means web extensions for Firefox won't work with Google Firebase because they only support chrome-extension.
Why the heck isn't it web-extension: ???
- amelius 6y agoIt could be, if you submit an RFC for a common format.
- arusahni 6y agoWebExtension was started by Mozilla, and is based on Chrome's extension API. Google has no incentive to support the project.
- asiando 6y agoIt’s funny that they have their own corner of the web where they own the entire API and the rest have to follow. Just because Mozilla and Apple share most of the API it doesn’t mean that Google won’t change it, in fact Manifest v3 is coming soon. Mozilla has implemented additional APIs that are never going back into Chrome because Google doesn’t care and doesn’t have to.
- Glench 6y agoAlthough Google is actually moving toward the standard in Manifest v3: https://developer.chrome.com/docs/extensions/mv3/intro/mv3-overview/ https://developer.chrome.com/docs/extensions/mv3/intro/mv3-o... (mostly with a Promise-based API)