This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Əgər kömək lazımdırsa lütfən yeni sual verin.

Firefox 62 broke the solution for "I want to open new tabs in a local page", how to repair?

  • 1 cavab
  • 1 has this problem
  • 1 view
  • Last reply by cor-el

FireFoxQuestions2
FireFoxQuestions2
more options

The solution posted here: https://support.mozilla.org/en-US/questions/1210576

worked wonderfully for providing an automatic load of a *local* homepage in a new tab until FF v62.0. I've checked my config file and js file, and both are correct and in the correct location, but now FF 62 broke this again. Two questions: *WHY*, and how do I force this back to the *obvious* choice of wanting a new tab to load your homepage (including *LOCAL*, no-net-needed, no junk, fast loading pages). No good explanation has ever been provided for why this simple functionality is forced away from users. This is *obvious* functionality, why is there not a good explanation of why FF developers won't provide their users with this capability.

The solution posted here: https://support.mozilla.org/en-US/questions/1210576 worked wonderfully for providing an automatic load of a *local* homepage in a new tab until FF v62.0. I've checked my config file and js file, and both are correct and in the correct location, but now FF 62 broke this again. Two questions: *WHY*, and how do I force this back to the *obvious* choice of wanting a new tab to load your homepage (including *LOCAL*, no-net-needed, no junk, fast loading pages). No good explanation has ever been provided for why this simple functionality is forced away from users. This is *obvious* functionality, why is there not a good explanation of why FF developers won't provide their users with this capability.

All Replies (1)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

In Firefox 62 the autoconfig file is run in a sandbox that doesn't support such privileged JavaScript code. You can probably see messages in the Browser Console about this change. It is also mentioned in the Release Notes. 

Updates for enterprise environments:

    AutoConfig is sandboxed to the documented API by default. You
    can disable the sandbox by setting the preference
    general.config.sandbox_enabled to false. Our long term plan is to
    remove the ability to turn off the sandboxing. If you need to
    continue to use more complex AutoConfig scripts, you will need to use
    Firefox Extended Support Release (ESR).

See also: