You could do this through a content script, but being able to alter the HTTP response body gives a whole new set of possibilities: function listener(details) ) This proxy information will let webRequest listeners determine how the request interacted with a proxy.Ī major new API for webRequest is now available which allows an extension to filter the HTTP response bodies as they come in. The webRequest details object now includes proxy information. This allows information about tabs or windows to survive session restores without the data needing to be stored by individual extensions. The session API now has some APIs for setting, getting and removing data on a per tab or per window basis. This allows extensions to track the opener of tabs.Īlso, the tabs API can now open URLs that are view-source: links and do a “ load replace” which changes the page and replaces the current history so that the back button is unaffected.
#Roboform firefox 57 webextenstions update#
The tabs.opener API has now been implemented which means that openerTabId is available to the update and create methods and on the Tab object. This is part of getting ready for a tabs.discard API. It will be set to true if the tab is not loaded with content, for example when restored from a previous session. Tabs now have a discarded state added to the Tab object.
When you do, be sure to tell them about it.ĭocumentation for the APIs discussed here can be found on MDN Web Docs. Just update your listing with the new code and your users will automatically update to the compatible version. Legacy add-ons no longer load in Firefox 57, but there is still time to migrate ( almost 5,000 have migrated so far!), and you can do so even after it lands in release. Firefox 57 has reached Beta, and a bevy of new APIs and improvements have landed that will put us in a good place for the Firefox Quantum launch in November.
0 kommentar(er)
