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

On Firefox 60 how do I get back the older equal size tiles with a new tab? I used to set browser.newtabpage.activity-stream.enabled to false but this now fails

more options

All in the question. I like the 'old' equal-size tiles and used to get this until a couple of weeks ago (or so). I set browser.newtabpage.activity-stream.enabled to false and it worked! Now it doesn't (again...). Can I have my style still, please?

All in the question. I like the 'old' equal-size tiles and used to get this until a couple of weeks ago (or so). I set browser.newtabpage.activity-stream.enabled to false and it worked! Now it doesn't (again...). Can I have my style still, please?

All Replies (4)

more options

Hi, you are running a beta, maybe next week they will be back.

Do you have a record of all the changes you have made in about:config ? Change things back.

As you can run both with the compatibility mode in Developer install and check the about:config settings and see if can match them.

Create a new empty Profile in 60 and see what the default is and then swap to the other Profile and make your changes in about:config.

No idea how to help you. usserChrome maybe, but it's a beta...always will be so there fore any changes made may not work next week. If this was Release Version 59.0.2 then can help.

Also if this is a bug, should be filing a bug report. https://bugzilla.mozilla.org/ Bug Writing Guidelines : https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines

more options

The "old" new tab page has gone away in beta.

You can use custom style rules in a userContent.css file to resize the tiles to be more similar to the old design. I looked into that briefly but didn't complete the project. The start was over here:

https://www.reddit.com/r/FirefoxCSS/comments/847qig/enlarge_tiles_site_thumbnails_on_new_tab_page/

Someone else may have posted a better suggestion, as that forum is full of style rule gurus.

more options

I thank both of you who replied very much - I will see what happens with the release version. What upsets me, as an open source fan, is not being given a choice. I would regard my 'problem' as one in the 'shell' surrounding the real firefox inards and I cannot see why changes are not purely optional since the old code probably exists and would run. Very Microsoft-like to tell me, as I suspect Mozilla are doing, the 'you take what we give you and like it'.

more options

Hi johndardis, this happens all the time: download manager removed in Firefox 26, certain insecure SSL ciphers removed in Firefox 36, old search bar removed in Firefox 43, legacy extensions disabled in Firefox 57. Change change change. The product people will tell you it slows down development, slows down performance, and makes debugging harder the more old code paths are maintained in the product after a change. I don't know how much slower or buggier, but that's my understanding of why we can't keep everything forever.