We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

How to remove fixed items from bookmarks menu

more options

The following css used to work to remove items from Bookmarks menu:

#bookmarksToolbarSeparator,#bookmarksMenuItemsSeparator{display: none !important;}
#bookmarksToolbarSeparator,#organizeBookmarksSeparator{display: none !important;}
#bookmarksToolbarSeparator,#menu_bookmarkAllTabs{display: none !important;}
#bookmarksToolbarSeparator,#bookmarksShowAll{display: none !important;}

It no longer works in FF88. How to fix?

N.B. There wasn't a way to hide "other bookmarks" from the bookmarks MENU (This has nothing to do with the unrelated TOOLBAR issue, and the settings for that do not affect the menu)

The following css used to work to remove items from Bookmarks menu: <pre><nowiki>#bookmarksToolbarSeparator,#bookmarksMenuItemsSeparator{display: none !important;} #bookmarksToolbarSeparator,#organizeBookmarksSeparator{display: none !important;} #bookmarksToolbarSeparator,#menu_bookmarkAllTabs{display: none !important;} #bookmarksToolbarSeparator,#bookmarksShowAll{display: none !important;}</nowiki></pre><br> It no longer works in FF88. How to fix? N.B. There wasn't a way to hide "other bookmarks" from the bookmarks MENU (This has nothing to do with the unrelated TOOLBAR issue, and the settings for that do not affect the menu)
已附加屏幕截图

由cor-el于修改

被采纳的解决方案

You can possibly leave a space at the start of a line to force rendering as a PRE tag.

The IDs you use look correct, so you can check for other issues like a hidden .txt appended or not having enabled userChrome.css.

Does other CSS code in userChrome.css still work in case you have more rules in your file ?


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
定位到答案原位置 👍 1

所有回复 (3)

more options

For reasons best known to itself the page replaced the hashes with the numbers 1-4 it ACTUALLY looked like this (... added to stop bizarre autoformatting)

... #bookmarksToolbarSeparator,#bookmarksMenuItemsSeparator{display: none !important;} ... #bookmarksToolbarSeparator,#organizeBookmarksSeparator{display: none !important;} ... #bookmarksToolbarSeparator,#menu_bookmarkAllTabs{display: none !important;} ... #bookmarksToolbarSeparator,#bookmarksShowAll{display: none !important;}

more options

选择的解决方案

You can possibly leave a space at the start of a line to force rendering as a PRE tag.

The IDs you use look correct, so you can check for other issues like a hidden .txt appended or not having enabled userChrome.css.

Does other CSS code in userChrome.css still work in case you have more rules in your file ?


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

Added spaces at the start of the line and moved the code to the top of the CSS. Did the trick, thanks.