ค้นหาฝ่ายสนับสนุน

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.

เรียนรู้เพิ่มเติม

How to rearange bookmarks layout in new/home tab?

  • 2 การตอบกลับ
  • 1 คนมีปัญหานี้
  • 4 ครั้งที่ดู
  • ตอบกลับล่าสุดโดย jscher2000 - Support Volunteer

more options

Hello,

Up until today my bookmarks in new tab looked like this - https://www.dedoimedo.com/images/computers_years/2012_1/firefox-13-new-tab-preview.jpg except 3 rows with 4 columns. Now there are 2 rows, 6 columns of extremely small bookmarks. How to roll back to big and nice looking bookmarks? My elderly parent's say new look is broken and why fix something that wasn't broken. This change causes huge usability problems for them.

Edit: Fixed by disabling switching from beta build back to 59. But now I know issue will reemerge when 60 will be stable.

Regards, Ramrr

Hello, Up until today my bookmarks in new tab looked like this - https://www.dedoimedo.com/images/computers_years/2012_1/firefox-13-new-tab-preview.jpg except 3 rows with 4 columns. Now there are 2 rows, 6 columns of extremely small bookmarks. How to roll back to big and nice looking bookmarks? My elderly parent's say new look is broken and why fix something that wasn't broken. This change causes huge usability problems for them. Edit: Fixed by disabling switching from beta build back to 59. But now I know issue will reemerge when 60 will be stable. Regards, Ramrr

เปลี่ยนแปลงโดย Ramrr เมื่อ

การตอบกลับทั้งหมด (2)

more options
more options

Hi Ramrr, I don't know why the top sites thumbnails are small now. ?? The "real" thumbnail images are still captured in a fairly large size, so it is possible to restyle the page using custom style rules in a userContent.css file.

Someone else asked about this the other day, so I started a discuss on it over on Reddit:

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

You could bookmark that thread for future reference, or I'm sure you'll see other (better) approaches suggested as Firefox 60 gets closer to release.