Windows 10 will reach EOS (end of support) on October 14, 2025. For more information, see this article.

搜索 | 用户支持

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

详细了解

Firefox 136 broke my custom new tab page, how do I fix it?

  • 9 个回答
  • 1 人有此问题
  • 182 次查看
  • 最后回复者为 firefox2506

more options

I'm on Linux.

I've been using this method to setup a custom new tab page for Firefox for almost 4 years, and it has worked great: https://jamesnorth.net/knowledge-base/article/firefox-new-tab-page

---

Navigate to /usr/lib/firefox.

Create autoconfig.cfg:

// var {classes:Cc,interfaces:Ci,utils:Cu} = Components;

/* set new tab page */ try {

 Cu.import("resource:///modules/AboutNewTab.jsm");  
 var newTabURL = "file:///home/james/ff/index.html";  
 AboutNewTab.newTabURL = newTabURL;  

} catch(e){Cu.reportError(e);} // report errors in the Browser Console

Create defaults/pref/autoconfig.js:

// pref("general.config.filename", "autoconfig.cfg"); pref("general.config.obscure_value", 0); pref("general.config.sandbox_enabled", false);

---

However, upon updating to Firefox 136, I only get a blank page. All of my autoconfig files still exist in /usr/lib/firefox.

When I create a new tab with Ctrl+T, it's a blank page. When I create a new window, it loads the local page I want it to load with the file path in the URL (which it never had before; the URL bar was blank in Firefox 135). So it seems to be partially working.

Any tips?

I'm on Linux. I've been using this method to setup a custom new tab page for Firefox for almost 4 years, and it has worked great: [https://jamesnorth.net/knowledge-base/article/firefox-new-tab-page https://jamesnorth.net/knowledge-base/article/firefox-new-tab-page] --- Navigate to /usr/lib/firefox. Create autoconfig.cfg: // var {classes:Cc,interfaces:Ci,utils:Cu} = Components; /* set new tab page */ try { Cu.import("resource:///modules/AboutNewTab.jsm"); var newTabURL = "file:///home/james/ff/index.html"; AboutNewTab.newTabURL = newTabURL; } catch(e){Cu.reportError(e);} // report errors in the Browser Console Create defaults/pref/autoconfig.js: // pref("general.config.filename", "autoconfig.cfg"); pref("general.config.obscure_value", 0); pref("general.config.sandbox_enabled", false); --- However, upon updating to Firefox 136, I only get a blank page. All of my autoconfig files still exist in /usr/lib/firefox. When I create a new tab with Ctrl+T, it's a blank page. When I create a new window, it loads the local page I want it to load with the file path in the URL (which it never had before; the URL bar was blank in Firefox 135). So it seems to be partially working. Any tips?

由firefox2506于修改

被采纳的解决方案

I saw something on this over on r/Firefox. Let me search... okay, yes, I haven't tested any of these myself:

In short, an internal file name changed, so you need to update that in your startup script.

AboutNewTab.jsm => AboutNewTab.sys.mjs

定位到答案原位置 👍 2

所有回复 (9)

more options

What custom page? How did you verify the page works with Firefox browser? The browser is a general browser for everyone and page if there is something on the page that doesn't match what Firefox browser latest version expects it most likely won't load or run it. And this comes down to security to prevent breakage of the browser itself so it can still work and be used.

more options

Hi Mark,

> What custom page?

My custom page. I created the .html and .css files for my own page that I want to display when I open a new tab. The way to get Firefox to display the page is to create the autoconfig files as detailed in the original question.

I verified that the page worked by using Firefox with this page for 4 years :)

The page is just simple HTML/CSS, as you'll see from the link in the original question. It still works when you open a new window in Firefox 136 - just not a new tab.

If this is a security feature, it's poorly-implemented because it only fails to load the page for new tabs and not new windows.

more options

If that's the case you should post that to a html or css forum for other programmers to review to see if there is issues with it and the browser it runs on to verify that it works as intented.

more options

I have removed the CSS and slimmed down the HTML. The entire HTML document is now just this (pictured in screenshot).

It displays in a new window. It does not display in a new tab. It works fine in Firefox 135 on my other computer, as it did for every version between 91 and 135 (and probably for many years before that).

Mozilla has clearly changed something. Perhaps I'll submit a bug to the bugzilla.

由firefox2506于修改

more options

Hey there, I have the same problem on Fedora 41. I can confirm the upgrade from version 135 to 136 is the cause. Rolling back to 135 makes the configuration work again.

@firefox2506 did you ever create a bug on the bugzilla? If so, mind posting a cross reference it here?

more options

@noassl Someone else had already created a bug and mine got merged as a duplicate.

The answer is essentially, "we're surprised it worked for as long as it did because this hasn't been supported for years."

https://bugzilla.mozilla.org/show_bug.cgi?id=1950457

more options

Oh, that's just great.

Thanks for the link anyway.

more options

选择的解决方案

I saw something on this over on r/Firefox. Let me search... okay, yes, I haven't tested any of these myself:

In short, an internal file name changed, so you need to update that in your startup script.

AboutNewTab.jsm => AboutNewTab.sys.mjs

more options

Thanks, jscher2000! I've updated my file and my new tab page now opens my custom file again.

I've updated my knowledgebase article to contain the updated code.