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

Este fío arquivouse. Faga unha nova pregunta se precisa axuda.

New tab setting keeps resetting to Google, how to make it stay empty?

  • 3 respostas
  • 2 have this problem
  • 6 views
  • Last reply by cahmar

cahmar
cahmar
more options

I have searched for a way to make my new tabs, which currently open to Google, open as empty instead. I found the way described on this site, which is to go in about:config and change the URL of browser.newtab.url to about:blank. Then, I closed Firefox, made sure it was fully closed in Task Manager, and then restarted it. I then tried to open a new tab, and it still automatically opened Google on the new tab. When I rechecked the URL of browser.newtab.url, it was back to having a value of chrome://quick_start/content/index.html.

I don't know whether this makes any difference or not, but I had Chrome open throughout this entire process. Chrome, however, is not my default browser.

I have searched for a way to make my new tabs, which currently open to Google, open as empty instead. I found the way described on this site, which is to go in about:config and change the URL of browser.newtab.url to about:blank. Then, I closed Firefox, made sure it was fully closed in Task Manager, and then restarted it. I then tried to open a new tab, and it still automatically opened Google on the new tab. When I rechecked the URL of browser.newtab.url, it was back to having a value of chrome://quick_start/content/index.html. I don't know whether this makes any difference or not, but I had Chrome open throughout this entire process. Chrome, however, is not my default browser.

Chosen solution

Hello,

Firefox uses the "chrome://" protocol to access its own internal files and also access files from extensions, so that has nothing to do with Google Chrome. 

   https://developer.mozilla.org/en/Chrome

So it looks like a problem with an extension.

Start Firefox in Safe Mode to check if one of the extensions or if hardware acceleration is causing the problem. 


   https://support.mozilla.org/kb/Safe+Mode
   https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes

Hope it helps.

Ler a resposta no contexto 👍 1

All Replies (3)

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

This is likely caused by one of the installed extensions and quick_start in the chrome URL should tell which extension in this case.

Start Firefox in Safe Mode to check if one of the extensions (Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem.

  • Switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance
  • Do NOT click the Reset button on the Safe Mode start window

There are other things that need your attention.

Please update to the current Firefox 31 release.

  • Help > About Firefox

The Firefox 14 version that you currently run is no longer supported with security updates.

  • It is important to update Firefox and add-ons to the latest version to get all security fixes.
Talha
Talha
more options

Chosen Solution

Hello,

Firefox uses the "chrome://" protocol to access its own internal files and also access files from extensions, so that has nothing to do with Google Chrome. 

   https://developer.mozilla.org/en/Chrome

So it looks like a problem with an extension.

Start Firefox in Safe Mode to check if one of the extensions or if hardware acceleration is causing the problem. 


   https://support.mozilla.org/kb/Safe+Mode
   https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes

Hope it helps.

cahmar
cahmar Question owner
more options

Thanks to both of you! It was actually this FastStart extension causing the issue. I don't remember installing it though, so I'm not sure where it came from.