Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

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

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

Disappearing Bookmarks Sidebar

  • 23 uphendule
  • 13 zinale nkinga
  • 589 views
  • Igcine ukuphendulwa ngu IanM

IanM
IanM

Everytime I load Firefox the bookmarks sidebar is not shown.

Navigating thus View => Sidebar => Bookmarks I can bring it up. It will stay visible for the whole of my browser session. However, after I've closed this session and started another. the bookmark sidebar is missing again.

How can I make the bookmarks sidr be available all the time?

FF 127.0.2 OS Windows 11 Pro v 24H2 Build(26100.994).

Everytime I load Firefox the bookmarks sidebar is not shown. Navigating thus View => Sidebar => Bookmarks I can bring it up. It will stay visible for the whole of my browser session. However, after I've closed this session and started another. the bookmark sidebar is missing again. How can I make the bookmarks sidr be available all the time? FF 127.0.2 OS Windows 11 Pro v 24H2 Build(26100.994).

Isisombululo esikhethiwe

Mozilla confirm that this is FIXED in v 133.x.x

Funda le mpendulo ngokuhambisana nalesi sihloko 👍 0

All Replies (3)

higitsune
higitsune

I just came across same issue with ver 132.0 and I believe, anyone using treestyle tab or sidebery or whatever kinda sidebar thingy should face this issue and I wonder how everybody tolerate that. Anyway I just wasted whole day for something officially bug and defection where there is no so solution And that advising guy doesn't even know/test how it's really like on their end. Completely useless.

IanM
IanM Umnikazi wombuzo

Mozilla have a patch for this issue, which is expected to in Firefox 133.x.x

IanM
IanM Umnikazi wombuzo

I can confirm that this issue has been fixed v 133.0

  1. 1
  2. 2