
When using tabs.executeScript() or tabs.insertCSS(): In Chrome: An extension can register a PAC file, but can also define explicit proxying rules.īecause this API is incompatible with Chrome's proxy API, the Firefox proxy API is only available through the browser namespace.In Firefox: An extension can register a PAC file.Waiting to make subsequent calls until within the () callback function is not a sufficient delay to prevent this.įirefox's proxy API followed a completely different design from Chrome's Proxy API.


In Firefox and Edge: JavaScript APIs are accessed under the browser namespace.See the "Browser compatibility" section in the manifest.json page for more details. Support for manifest.json keys differs across browsers.See Browser support for JavaScript APIs for more details. Support for JavaScript APIs differs across browsers.However, there are significant differences between Chrome, Firefox, and Edge. As far as possible, extensions written for those browsers should run on Firefox with minimal changes. Differences between API implementationsĮxtensions built with WebExtension APIs are designed to be compatible with Chrome and Opera extensions.
