Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

ابحث في الدعم

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

The menu has become too large a distance between the lines

  • 8 ردود
  • 1 has this problem
  • 6 views
  • آخر ردّ كتبه denleehar

more options

The menu (Bokmarks )has become too large a distance between the lines. Now the menus are getting way too long. Hard to read links and hard to find! Why this completely idiotic design change?

The change in the appearance of the tabs is also strange!

Is it possible to change back to the usual menu line spacing ???

The menu (Bokmarks )has become too large a distance between the lines. Now the menus are getting way too long. Hard to read links and hard to find! Why this completely idiotic design change? The change in the appearance of the tabs is also strange! Is it possible to change back to the usual menu line spacing ???

All Replies (8)

more options

Workmanen said

The menu (Bokmarks )has become too large a distance between the lines. Now the menus are getting way too long. Hard to read links and hard to find! Why this completely idiotic design change? The change in the appearance of the tabs is also strange! Is it possible to change back to the usual menu line spacing ???

Forgot to write which version I have: 89.0 (64-bit). The menus were destroyed when updating to version 89.0.

more options

You can use code in userChrome.css to modify the menu spacing.

more options

cor-el said

You can use code in userChrome.css to modify the menu spacing.

THANKS!!! Where can I find "userChrome.css"?

more options

It is not that difficult to create userChrome.css if you have never used it.

The first step is to open the "Help -> Troubleshooting Information" page and find the button to access the profile folder.

You can find this button under the "Application Basics" section as "Profile Folder -> Open Folder". If you click this button then you open the profile folder in the Windows File Explorer. You need to create a folder with the name chrome in this folder (name is all lowercase). In the chrome folder you need to create a plain text file with the name userChrome.css (name is case sensitive). In this userChrome.css text file you paste the text posted. On Mac you can use the TextEdit utility to create the userChrome.css file as a plain text file.

In Windows saving the file is usually the only time things get more complicated because Windows can silently add a .txt file extension and you end up with a file named userChrome.css.txt. To avoid this you need to make sure to select "All files" in the dialog to save the file in the text editor using "Save File as".

You need to close (Quit/Exit) and restart Firefox when you create or modify the userChrome.css file.

See also:

In Firefox 69 and later you need to set this pref to true on the about:config page to enable userChrome.css and userContent.css in the chrome folder.

  • toolkit.legacyUserProfileCustomizations.stylesheets = true
more options

THANKS!! I will look at your suggestions and come back if it works.

more options

I have now tested all the suggestions in the texts above. I have also read all the links and tested what is suggested there. None of it works, Firefox does not respond to any of it at all. It's still the same appearance.

I do not understand what is good about making the distance between the text in "Bookmarks" so large? Now it looks like it's a book for very young children! I want to talk to the one who came up with the idiotic idea !!

Back to .css: What do I do wrong when what I do is not visible in the browser?

more options

I have been working for a while and made it work !!! It seems that you have to wait a few minutes before some changes work.

more options

Welcome to Version 91.0 (64-bit), August 12 or 13, 2021. The problem has returned. The previous fix at about:config doesn't work this time.