Mozilla developers the from the Firefox codebase of user-accessible settings to disable multi-process operation (e10s). The reason for ceasing support for reverting to single-process mode is its low security and potential stability issues due to lack of full testing coverage. Single-process mode is deemed unsuitable for everyday use.
Starting with Firefox 68, the settings "browser.tabs.remote.force-enable" and
"browser.tabs.remote.force-disable", which control the enabling of e10s. Additionally, setting the value of "false" in the "browser.tabs.remote.autostart" option will no longer automatically disable multi-process mode on desktop versions of Firefox, in official builds, and when launched without enabling the automated testing mode.
In mobile builds, during testing (with the environment variable MOZ_DISABLE_NONLOCAL_CONNECTIONS active or the "—disable-e10s" option) and in unofficial builds (without MOZ_OFFICIAL), the "browser.tabs.remote.autostart" option will still be applicable to disable e10s. For developers, a workaround has also been added to disable e10s, implemented by setting the environment variable "MOZ_FORCE_DISABLE_E10S" before launching the browser.
Additionally, it can be noted the plan to discontinue support for TLS 1.0 and 1.1 in Firefox. In March 2020, the possibility of establishing a secure connection using TLS 1.0 and 1.1 will be removed, and attempts to open sites that do not support TLS 1.2 or TLS 1.3 will result in an error. In nightly builds, support for outdated TLS versions will be disabled in October 2019.
The discontinuation of support is coordinated with developers of other browsers, and the ability to use TLS 1.0 and 1.1 will also cease at the same time in Safari, Firefox, Edge, and Chrome. Website administrators are recommended to ensure support for at least TLS 1.2, preferably TLS 1.3. Most sites have already transitioned to TLS 1.2; for example, out of one million verified hosts, only 8,000 do not support TLS 1.2.
Source: opennet.ru
