Ref:
The extension currently explicitly uses the chrome namespace to access the WebExtensions API. While the sub-namespaces and methods in there are agnostic to all major browsers (at least since Chrome MV3), using the standard browser namespace is much preferred to maximize compatibility.
The hope is that we can either:
- Switch the namespace to
browser entirely, or
- Stub the
browser namespace with either chrome or browser depending on the environment
Feedback and concerns are welcome
Ref:
The extension currently explicitly uses the
chromenamespace to access the WebExtensions API. While the sub-namespaces and methods in there are agnostic to all major browsers (at least since Chrome MV3), using the standardbrowsernamespace is much preferred to maximize compatibility.The hope is that we can either:
browserentirely, orbrowsernamespace with eitherchromeorbrowserdepending on the environmentFeedback and concerns are welcome