In Firefox 68, we are introducing a new API and some enhancements to webRequest and private browsing. We’ve also fixed a few issues in order to improve compatibility and resolve issues developers were having with Firefox.<\/p>\n
At airports and caf\u00e9s you may have seen Firefox asking you to log in to the network before you can access the internet. In Firefox 68, you can make use of this information in an extension. The new captive portal API will assist you in making sure your add-on works gracefully when locked behind a captive portal.<\/p>\n
For example, you could hold off your requests until network access is available again. If you have been using other techniques for detecting captive portals, we encourage you to switch to this API so your extension uses the same logic as Firefox.<\/p>\n
Here is an example of how to use this API:<\/p>\n
(<\/span>async function<\/span>(<\/span>)<\/span> {<\/span>\r\n \/\/ The current portal state, one of `unknown`, `not_captive`, `unlocked_portal`, `locked_portal`.<\/span>\r\n let<\/span> state =<\/span> await browser.<\/span>captivePortal.<\/span>getState(<\/span>)<\/span>;<\/span>\r\n\r\n \/\/ Get the duration since the captive portal state was last checked<\/span>\r\n let<\/span> lastChecked =<\/span> await browser.<\/span>captivePortal.<\/span>getLastChecked(<\/span>)<\/span>;<\/span>\r\n\r\n console.<\/span>log<\/span>(<\/span>`<\/span>The captive portal has been <\/span>${<\/span>state<\/span>}<\/span> since at least <\/span>${<\/span>lastChecked<\/span>}<\/span> milliseconds<\/span>`<\/span>)<\/span>;<\/span>\r\n\r\n browser.<\/span>captivePortal.<\/span>onStateChanged.<\/span>addListener(<\/span>(<\/span>details)<\/span> =<\/span>><\/span> {<\/span>\r\n console.<\/span>log<\/span>(<\/span>\"<\/span>Captive portal state is: <\/span>\"<\/span> +<\/span> details.<\/span>state)<\/span>;<\/span>\r\n }<\/span>)<\/span>;<\/span>\r\n\r\n browser.<\/span>captivePortal.<\/span>onConnectivityAvailable.<\/span>addListener(<\/span>(<\/span>status)<\/span> =<\/span>><\/span> {<\/span>\r\n \/\/ status can be \"captive\" in an (unlocked) captive portal, or \"clear\" if we are in the open<\/span>\r\n console.<\/span>log<\/span>(<\/span>\"<\/span>Internet connectivity is available: <\/span>\"<\/span> +<\/span> status)<\/span>;<\/span>\r\n }<\/span>)<\/span>;<\/span>\r\n}<\/span>)<\/span>(<\/span>)<\/span>;<\/span>\r\n<\/pre>\nNote: if you use this API, be sure to add the captivePortal permission to your manifest.<\/p>\n
Private and contained<\/h1>\n
We\u2019ve made a few additions to the webRequest API<\/a> to better support private browsing mode. You can now limit your webRequests to only include requests from private browsing mode. If instead you are interested in both types of requests it is now possible to differentiate them in the webRequest listener.<\/p>\nTo improve the integration of containers, we\u2019ve also added the container ID (cookieStoreId) to the webRequest listener.<\/p>\n
Proxy new and proxy old<\/h1>\n
The two additional fields mentioned in the previous section are also available in the details object passed to the proxy.onRequest<\/a> listener.<\/p>\nAt the same time, we\u2019d like to make you aware that we are deprecating the proxy.register<\/code>, proxy.unregister<\/code> and proxy.onProxyError<\/code> APIs. As an alternative, you can use the proxy.onRequest<\/a> API to determine how requests will be handled, and proxy.onError<\/a> to handle failures. If your extension is using these APIs you will see a warning in the console. These APIs will ultimately be removed in Firefox 71, to be released on December 10th, 2019.<\/p>\nTiming is everything<\/h1>\n
We\u2019ve changed the timing of tabs.duplicate<\/a> for better compatibility with Chrome. The promise is now resolved immediately, before the duplicated tab finished loading. If you have been relying on this promise for a completed duplicated tab in Firefox, please adjust your code and make use of the tabs.onUpdated<\/a> listener.<\/p>\nMiscellaneous<\/h1>\n\n- \n
\n- Since extensions cannot add bookmarks to the root folder, we\u2019ve improved the error message you get when you try.<\/li>\n
- If you’ve been trying to remove indexedDB data via
browser.browsingData.remove({}, { indexedDB: true });<\/code> and it failed in some cases, we\u2019ve fixed this on our end now.<\/li>\n- Removing cookies for IPv6 addresses has been fixed.<\/li>\n
- Fixes an issue when setting cookies with an IP address in the domain field, along with the url field being set.<\/li>\n
- Hard-to-debug performance issues using webRequest.onBeforeRequest with requestBody during large uploads have been solved.<\/li>\n
- An issue with identity.launchWebAuthFlow<\/a> hanging after authentication has been resolved.<\/li>\n
- storage.onChanged<\/a> is now fired when values are removed.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n
Thank You<\/h1>\n
We’ve had a great amount of support from the community. I’d like to thank everyone who has taken part, but especially our volunteer contributors Jan Henning, Myeongjun Go, Oriol Brufau<\/a>, M\u00e9lanie Chauvel<\/a>, violet.bugreport and Piro<\/a>. If you are interested in contributing to the WebExtensions ecosystem, please take a look at our wiki<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"