This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

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

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.

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

Private browser closed on its own. Launching new and toolbar bookmark area empty, both private and regular browser.

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

more options

Desktop 121.0.1

A private browser closed on its own. A new private browser launch and the toolbar bookmark area is empty. A regular browser launched and still the toolbar bookmark area is empty. The bookmarks are not erased, they just are no longer present in the toolbar bookmark area.

Desktop 121.0.1 A private browser closed on its own. A new private browser launch and the toolbar bookmark area is empty. A regular browser launched and still the toolbar bookmark area is empty. The bookmarks are not erased, they just are no longer present in the toolbar bookmark area.
ภาพหน้าจอที่แนบมา

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

more options

Go into Customize mode and drag "Bookmark toolbar items" into the bookmarks toolbar. Alternatively, click the "Restore Defaults" button in the bottom-right corner.

more options

I had gone in there. I did not find customize at first, but did locate it. That area where the folders were supposed to be, showed to me that they were 'still' supposed to be there. I did not think to include a screenshot of that.

Though before reporting, opening and closing private and regular browser windows, all remained empty. After, and I mean right after submitting....the next private browser window opened and all the folders were present. I didn't report that, in hopes to understand "WHY" that occurred & how to rectify if ever happened again (never seen this issue before).