Additional corrective releases have been published in quick succession. and , which continues the work on restoring extensions disabled due to .
In particular, it resolves the issue with updating the intermediate certificate when a master password is set, which controls access to the stored credentials database. Since replacing the certificate requires the master password to be entered, as
to this issue, any action that requires entering the master password can be taken (for example, requesting the viewing of saved passwords or initiating the autofill of a saved login form).
Additionally, several recent developments related to Firefox can be noted:
- In Firefox 67 and 68 the number of API calls that only applies when opening a page in a secure context (), i.e., when opened over HTTPS, via localhost, or from a local file. In Firefox 67, for pages opened outside of a secure context, system notifications via the API , shown outside the browser window. In Firefox 68, unprotected requests will block the calls for to access multimedia data sources (such as the camera and microphone). It should be noted that these restrictions have already been in place since Chrome 62 and 47.
- In , which form the basis of the Firefox 68 release, the implementation of the address bar. The Awesome Bar has been replaced by the Quantum Bar. From a user's perspective, with few exceptions, everything remains as it was, but the internals and the code has been rewritten, replacing XUL/XBL with the standard Web API.
The new implementation significantly simplifies the process of extending functionality (support for creating extensions in the WebExtensions format is available), removes rigid ties to the browser subsystems, allows easy integration of new data sources, and provides higher performance and responsiveness of the interface.
Notable changes in behavior include the requirement to use the Shift+Del or Shift+BackSpace combinations (previously it worked without Shift) to delete browsing history entries from the suggestions displayed when input begins. - the process of phasing out the classic Firefox editor for Android in favor of a new mobile browser being developed within the project that uses the GeckoView engine and a set of libraries. , which are already being used to build browsers and . GeckoView is a variant of the Gecko engine presented as a separate library that can be updated independently, and Android Components includes libraries with standard components that ensure the operation of tabs, input autocompletion, search suggestions, and other browser features.
Firefox 68 will be the last release that includes an update for the classic version of Firefox for Android. Starting with Firefox 69, which is expected on September 3, new releases of Firefox for Android will not be issued. , and fixes will be provided as updates to the Firefox 68 ESR branch. Currently, Fenix
is preparing to begin beta testing and is still lagging behind Firefox for Android in terms of functionality. The first stable release of Fenix 1.0 is expected in June, and the release of Fenix 2.0 is planned for mid-August.
Source: opennet.ru
