- ECHOFON FIREFOX FOR FIREFOX 57 UPDATE
- ECHOFON FIREFOX FOR FIREFOX 57 CODE
- ECHOFON FIREFOX FOR FIREFOX 57 SERIES
- ECHOFON FIREFOX FOR FIREFOX 57 WINDOWS
Of course, developers following the Mozilla blogs have been aware of this change for a while. Those who maintain their own extensions should read through the general upstream documentation on the change and the specific porting guide, as well.
The compatibility roadmap has been known for the past year. This shouldn’t be a surprise to Firefox extension developers, though. Starting with version 57, Firefox supports only a new type of extension, named WebExtension. Firefox 57 marks an end to the legacy XUL based extensions. It was an important milestone date for the various Firefox add-ons. This deadline gave third party developers a chance to look at their extensions and make changes to remain compatible. These changes mark a major deadline for how extensions work. Last month the major changes landed in the developer channel. Some improvements arrived already with no major differences for its users. These changes are referred to as Project Quantum.
ECHOFON FIREFOX FOR FIREFOX 57 SERIES
Over the past year, Mozilla has been working on a series of major changes to the Firefox browser, mainly for performance and security. One of those rare situations is happening at present. However, there are times an upstream provides a path that makes this unavoidable. Of course they always try to avoid any breaking changes to the user experience. The maintainers do their best to handle these situations. The kernel is one of these, and Firefox is another. In Firefox you can place a JSON file in a directory, just like for native messaging.A few packages in Fedora get major updates outside the regular release cycle. This allows administrators or other applications to configure extensions for users. Str = str.replace(/Example/g, 'WebExtension Example') ī(Ī basic implementation of has landed. 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.
ECHOFON FIREFOX FOR FIREFOX 57 WINDOWS
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.
ECHOFON FIREFOX FOR FIREFOX 57 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.
ECHOFON FIREFOX FOR FIREFOX 57 CODE
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)
