Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

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

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

  • 4 replies
  • 0 have this problem
  • 4 views
  • Last reply by 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?

Modified by firefox2506

All Replies (4)

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.

Helpful?

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.

Helpful?

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.

Helpful?

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.

Modified by firefox2506

Helpful?

Ask a question

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.