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

How do I display more icons on the New-Tab page? I tried about:config

  • 3 பதிலளிப்புகள்
  • 1 இந்த பிரச்சனை உள்ளது
  • 1 view
  • Last reply by CoryMH

The New-Tab page I see doesn't match what FF shows in help. I changed rows and columns and nothing changed.

The New-Tab page I see doesn't match what FF shows in help. I changed rows and columns and nothing changed.

All Replies (3)

Hello,

With the latest Firefox update, the number of tiles is now determined on screen size - if you zoom out or expand the window you can have more tiles appear.

If you want to set a fixed number of tiles, you can do so with the following extension:

You can also see jscher2000's Chosen Solution here: https://support.mozilla.org/en-US/questions/1025414 It requires the Stylish add-on but will automatically shrink the tiles on the page and will limit the tiles based on what you entered for your rows and columns in the about:config page:

Thanks. add-ons are a last resort IMO (I have enough memory problems already) but I'll do it if I can't find another workaround.

I didn't see any ref to tiles & screen-size in the help. Did I miss it?

about:config still lets you set rows & columns - that's just for add-ons then?

When you zoom out on the new tab page, the number of tiles is limited to the rows and columns settings in the about:config. Unfortunately I don't know how to maintain the zoom settings for new instances of the "about:newtab" page.

What you can try is create a userChrome.css file to change the appearance of your about:newtab page (which is essentially what the Stylish script does). You can click "Show CSS" on that page to figure out what you need to add to the file: https://userstyles.org/styles/106326/shrink-new-tab-thumbnails

Articles about the userChrome.css file:

Note: I recommend using Stylish because it makes changes to the interface easier to manage than creating the userChrome.css file. You should check to see if you experience any significant impacts using the extension and then go the userChrome.css route if you find that there are.