Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

Annoying changes in the new tab page of Firefox 31

  • 3 antwoorden
  • 42 hebben dit probleem
  • 4 weergaven
  • Laatste antwoord van ManuelFte

more options

I just upgraded to Firefox 31 and I've detected two annoying changes in the new tab page.

First, the new search box, I don't need it at all because I use search engines with keywords in the address bar and I'd like to know how to remove it.

Second, I had configured the new tab page to display 42 thumbnails (6 columns and 7 rows) and now it only shows 8 thumbnails. In the about:config the settings are still as I had them but only 8 thumbnails are shown no matter what number is set.

Can anyone tell me how to solve these problems without downgrading?

I just upgraded to Firefox 31 and I've detected two annoying changes in the new tab page. First, the new search box, I don't need it at all because I use search engines with keywords in the address bar and I'd like to know how to remove it. Second, I had configured the new tab page to display 42 thumbnails (6 columns and 7 rows) and now it only shows 8 thumbnails. In the about:config the settings are still as I had them but only 8 thumbnails are shown no matter what number is set. Can anyone tell me how to solve these problems without downgrading?

Gekozen oplossing

I didn't know about the existence of those archives. I investigated a bit and after a few tests with Firebug I got this code:

@-moz-document url(about:newtab) {

#newtab-margin-undo-container, #newtab-margin-top, #newtab-search-container, #newtab-search-logo {

display:none !important; }

#newtab-grid {

height: 650px !important; max-height: 650px !important; }

.newtab-cell {

height: 9% !important; width: 13% !important; } }

That combines your codes, hides another top margin and resizes the thumbnails in order to fit the 42 squares to my resolution (1280x800). Obviously the values ​​must be modified to be adapted to other number of thumbnails and resolutions. If anyone knows any more generic solution I'll be happy to hear it. I also hope that Mozilla fix this bug to avoid having to do this process. Thanks for your help. :)

Dit antwoord in context lezen 👍 10

Alle antwoorden (3)

more options

You can add the following CSS code into your userChrome.css file to hide the search box.

 
@-moz-document url(about:newtab) 
{
  #newtab-search-container, #newtab-search-logo { display:none !important; } 
  } 
more options

You may also want to suppress the large margin at the top.

Note tha the his code should be in userContent.css and not in userChrome.css

/* about:newtab */
@-moz-document url(about:newtab){
#newtab-margin-top {display:none!important}
#newtab-search-container {display:none!important}
}

The customization files userContent.css (websites) and userChrome.css (user interface) are located in the chrome folder in the Firefox profile folder.

  • Create the chrome folder (lowercase) in the <xxxxxxxx>.default profile folder if this folder doesn't exist
  • Paste the code in the userContent.css file
more options

Gekozen oplossing

I didn't know about the existence of those archives. I investigated a bit and after a few tests with Firebug I got this code:

@-moz-document url(about:newtab) {

#newtab-margin-undo-container, #newtab-margin-top, #newtab-search-container, #newtab-search-logo {

display:none !important; }

#newtab-grid {

height: 650px !important; max-height: 650px !important; }

.newtab-cell {

height: 9% !important; width: 13% !important; } }

That combines your codes, hides another top margin and resizes the thumbnails in order to fit the 42 squares to my resolution (1280x800). Obviously the values ​​must be modified to be adapted to other number of thumbnails and resolutions. If anyone knows any more generic solution I'll be happy to hear it. I also hope that Mozilla fix this bug to avoid having to do this process. Thanks for your help. :)

Bewerkt door ManuelFte op