The Mozilla developers have announced the removal from Firefox's codebase of user-accessible settings to disable multi-process operation (e10s).
The reason from completion of assistance to return to single process mode is its low security and possible stability problems due to lack of full coverage during testing.
Thereby will be marked by the developers as unsuitable for everyday use in the browser.
Firefox returns to single process mode
Starting with Firefox version 68 in config, the configurations will be removed "Browser.tabs.remote.force-enable" y "Browser.tabs.remote.force-disable", controlling the inclusion of e10s.
Also, setting the value to "false" in the "browser.tabs.remote.autostart" option will not automatically disable multiprocessor mode in the desktop versions of Firefox, in the official versions and in the unenabled release. automated testing.
While in the versions of Firefox for the different mobile devices, when testing (with environment variable active MOZ_DISABLE_NONLOCAL_CONNECTIONS or the "–disable-e10s" option) and in unofficial versions (without MOZ_OFFICIAL), the option "Browser.tabs.remote.autostart" can still be used to disable e10s.
For developers, a workaround to disable e10s has also been added, implemented via environment variable setting "MOZ_FORCE_DISABLE_E10S" before starting the browser.
Other changes for Firefox
As of Firefox version 66, by default se will set the number of default processes from the content controller, in which it has increased from 4 to 8 (Optionally, a process can be selected, but this does not disable multiprocessor mode, but implies that, in addition to the process to generate the interface, an additional process will be started to process the content).
Also, to mark the publication of a plan to discontinue support for TLS 1.0 and 1.1 in Firefox. In March 2020, the ability to establish a secure connection with TLS 1.0 and 1.1 will be removed and attempting to open sites that do not support TLS 1.2 or TLS 1.3 will fail.
While in versions of Firefox Nightly this support for outdated versions of TLS will be disabled in October 2019.
Finally it is also important to mention that termination of TLS 1.0 support is coordinated with developers of other browsers and the ability to use TLS 1.0 and 1.1 at the same time will end in Safari, Firefox, Edge, and Chrome.
Since as part of a movement coordinated between Four of the biggest names in technology, the old security protocols TLS 1.0 and 1.1 will be phased out in Safari, Edge, Internet Explorer, Firefox, and Chrome in 2020.
This is based on their coming together last year to purge the internet of these old and faulty protocols, noting that most people have now moved to TLS 1.2, if not TLS 1.3.
Browser developers Firefox, Chrome, Edge and Safari they warned of the imminent end of support for the TLS 1.0 and TLS 1.1 protocols:
- In Firefox, TLS 1.0 / 1.1 support will be discontinued in March 2020, but these protocols will be disabled earlier in trial and nightly versions.
- In Chrome, TLS 1.0 / 1.1 support will be discontinued as of Google Chrome version 81, which is expected in January 2020.
- While in Google Chrome version 72, which will be released in January 2019, when opening sites with TLS 1.0 / 1.1, a special warning about using the outdated version of TLS will be displayed. The settings that make it possible to return support for TLS 1.0 / 1.1 will remain until January 2021.
- In the Safari web browser and the WebKit engine, support for TLS 1.0 / 1.1 will be discontinued in March 2020.
- While in the Microsoft Edge web browser and Internet Explorer 11, the removal of TLS 1.0 and TLS 1.1 is expected in the first half of 2020.
As a last reminder that we mention, Due to the incident with plugins closure, the launch of Firefox 67 has been postponed for a week and will be released only on May 21.
The shift schedule for the preparation of the remaining pitches will not be.