Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

How to disable browser.tabs.remote.autostart.2 as default?

  • 3 个回答
  • 10 人有此问题
  • 1 次查看
  • 最后回复者为 cor-el

more options

I need to disable by default "browser.tabs.remote.autostart.2" to false. When changed manually to false after browser restart it's true again. Normally I use GPO to deploy js files to folder: C:/[Firefox folder]/defaults/pref

Example js file content I use: pref("security.enterprise_roots.enabled", true);

It works perfectly. But I can't set "browser.tabs.remote.autostart.2" with this way. Try lockPref, user_pref, defaultPref etc. I also deleted extension "e10srollout@mozilla.org.xpi" but multi-processor is still on (by default, at about:config it says "by user"). I can't change the parameter manually because of the size of the work environment (300+ hosts)

Mainly: OS: Windows 7 Pro - 32 and 64 bit and Firefox: usually 52 and above (all ESR)

Why I must to disable it? Agents from software that collect data from PC (and send it to log server) can't read URLs when this option is enable (IE and other browers are fine). Agents works in OS, not as extension in Firefox.

I need to disable by default "browser.tabs.remote.autostart.2" to false. When changed manually to false after browser restart it's true again. Normally I use GPO to deploy js files to folder: C:/[Firefox folder]/defaults/pref Example js file content I use: pref("security.enterprise_roots.enabled", true); It works perfectly. But I can't set "browser.tabs.remote.autostart.2" with this way. Try lockPref, user_pref, defaultPref etc. I also deleted extension "e10srollout@mozilla.org.xpi" but multi-processor is still on (by default, at about:config it says "by user"). I can't change the parameter manually because of the size of the work environment (300+ hosts) Mainly: OS: Windows 7 Pro - 32 and 64 bit and Firefox: usually 52 and above (all ESR) Why I must to disable it? Agents from software that collect data from PC (and send it to log server) can't read URLs when this option is enable (IE and other browers are fine). Agents works in OS, not as extension in Firefox.

被采纳的解决方案

Thanks for the answer.

From article Firefox in an enterprise environment I created:

file #1 - "C:\[FF installation folder]\defaults\pref\[config-pointer].js" contains: // Any comment. You must start the file with a comment! pref("general.config.filename", "[config-file].cfg"); pref("general.config.obscure_value", 0);

file #2 - "C:\[FF installation folder]\[config-file].cfg - for example: // Any comment. You must start the file with a comment! pref("security.enterprise_roots.enabled", true); pref("browser.tabs.remote.autostart.2", false);

Yes, file [config-file].cfg must be in main FF folder. If you have more .js files in "defaults\prefs" which contains the same value settings (like pref("security.enterprise_roots.enabled", true);) - delete it and put into .cfg file.

定位到答案原位置 👍 0

所有回复 (3)

more options

If about:support (not about:config) says Enabled by user instead of Enabled by default, that means something in your environment is overriding the browser.tabs.remote.autostart.2 preference in about:config, or at least causing it to get toggled back after restart. Are you saying the preference behaves like it’s not getting saved at all? I’m almost sure it should just stay as set, or something might prevent it from getting saved.

Note that in order to disable e10s, browser.tabs.remote.autostart also needs to be set to false. Also, the browser.tabs.remote.autostart.2 preference is ignored and overridden by browser.tabs.remote.force-enable if that may have been added in the past and set to true (?). However, both autostart preferences should still display as false in about:config in that case, and about:support should display "Enabled by user". I’m not aware of any other preferences overriding or even reverting these changed ones, but there may be some. (Generally it’s harder to force enabling e10s than disabling it, as could happen with add-ons or accessibility.)

If there is no browser.tabs.remote.force-enable preference involved, perhaps you could:

- Double-check all methods used for modifying preferences - Use the current profile’s prefs.js file and test the same on a non-corporate system, or just look at the file after changing browser.tabs.remote.autostart.2 after closing Firefox to see if it gets saved properly - Quickly test with a new/fresh profile and compare both profile’s prefs.js files if needed - Have a look at this question, as well as this bug

If changing the preference manually works, I think deploying it in a js file should work as well.

more options

选择的解决方案

Thanks for the answer.

From article Firefox in an enterprise environment I created:

file #1 - "C:\[FF installation folder]\defaults\pref\[config-pointer].js" contains: // Any comment. You must start the file with a comment! pref("general.config.filename", "[config-file].cfg"); pref("general.config.obscure_value", 0);

file #2 - "C:\[FF installation folder]\[config-file].cfg - for example: // Any comment. You must start the file with a comment! pref("security.enterprise_roots.enabled", true); pref("browser.tabs.remote.autostart.2", false);

Yes, file [config-file].cfg must be in main FF folder. If you have more .js files in "defaults\prefs" which contains the same value settings (like pref("security.enterprise_roots.enabled", true);) - delete it and put into .cfg file.

more options

There is a browser.tabs.remote.force-disable pref that you can try to lock to true.

  • lockPref("browser.tabs.remote.force-disable", true);

Note that Firefox comes with the e10srollout extension in the browser/features folder that might override/modify some settings at a later time.

由cor-el于修改