![Firefox logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2020-04-14-08-36-13-8dda6f.png)
New Tab doesn't show all tiles in Firefox 33
So I just updated to Firefox 33 and the first thing I notice is the newtab page is changed. I get a 4 x 2 grid instead of the regular 3 x 3 grid. I tried changing things through about:config and it says I should have a 5 x 3 grid. I can only decrease the number of columns and rows to see any change on the tab. If I shrink the tab using ctrl - it'll show things correctly but that doesn't save. What can I do to get newtab back to the way it was before updating or show things correctly?
所有回复 (10)
That can happen if the window isn't wide enough to accommodate for all the thumbnails. Firefox automatically adjust the number of columns to suit the current width to the screen and doesn't make the thumbnails smaller. You would have to zoom out to achieve that.
Same issue here.
Yesterday with FF32 I had a 3x3 grid of tiles on the newtab page. Today with FF33 I have 3x2 i.e. the number of columns is the same but the row count has decreased. The size of my screen has not changed.
I've checked in about:config and browser:newtabpage:columns is still set to 5 and browser:newtabpage:rows is still set to 3.
It seems that FF33 has decided to make the thumbnails larger for some reason.
Therefore, is it possible to reduce the thumbnail size back to how it was?
Same Issue Here...
Today, after applying update patch for Firefox 33.0, I found after restart it, the page NewTab only shows me some of the thumbnails (I have set 4x4, and prior to the update I was working properly, and now it shows me 4x2), and furthermore, these they are much larger, huge... I didn't found any setting to modify in about:config to get back to previous view, even changing rows and columns to default value of 3x3, but always it shows 2 rows with large thumbnails. But, when I check Page Info option on this new NewTab, I can see it has all thumbnails/objects loaded. I'm attaching some screen captures that maybe can be helpful.
Regards
Overall, I am seeing real strange "stuff" with the number of rows set in about:config and the number of columns set also, in multiple separate Profile in Firefox 33. I haven't been able to see any "order" in the chaos, as far as trying to pin down the fault.
browser.newtabpage.columns has a default setting of 5 which was set at 3 in prior versions, with browser.newtabpage.rows at 3, which was the previous value, too. Whatever I set those two prefs at, the maximum I see is 3 columns and 2 rows. Looks like a Bug to me.
Meanwhile, another Profile that I use - New Tab Tools - in, is humming along unaffected in Firefox 33.
I'm having a problem as well. I'm visually impaired, so have my fonts set fairly large, but Firefox has always displayed the 3x3 grid. Now I'm down to 2x2, and can't get anything more than that even when I zoom all the way out. I tried playing with the column setting listed above, but it had no effect. Something's definitely been broken with this update.
Note that there will be more changes in Firefox 34. Bug 1026561 - The New Tab Page should be smarter about showing more tiles when on large screens Bug 1005596 - Aurora31.0a2: Starting a new tab does not honor custom rows and columns Bug 978338 - Update new tab site rendering for fixed ratio tile images
The problem is the Mozilla changed the behaviour of the newtab page function without testing or Q&A. Scaling has little to do with it in as much as it worked fine before, then they fiddled with the code, now it doesn't work.
Dr_Shred that is your opinion about not having enough testing or QA. It was a stupid changes that has nothing to do with testing or QA; another case of making changes for mobile devices and kissing off the desktop crowd. Simple as that.
Well, how to force FF to remember scale settings of a new tab? Every single time i need to change it, TI'S SO ANNOYING
When is version 34 coming out? I am having this problem now too after FF lost the page to begin with (had to close and reopen the browser to correct that). I did not think I was too greedy in wanting 16 tiles instead of 9.
Please fix this.