為了改善您的使用體驗,本網站正在進行維護,部分功能暫時無法使用。若本站的文件無法解決您的問題,想要向社群發問的話,請到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 發問,我們的社群成員將很快會回覆您的疑問。

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

"Bookmarks Toolbar" problem

  • 1 回覆
  • 0 有這個問題
  • 6 次檢視
  • 最近回覆由 cor-el

more options

I have been dealing with an annoying problem after the latest update. I have some folders with multiple addresses on my "Bookmarks Toolbar" to check out some sites and accounts daily (Figure 1). Each folder contains more than one page (Figure 2) of bookmarks and I scroll down to open 10-12 addresses each time (Figure 2/3).

Before the update, there wasn't any problem and when I came back to the folder I could continue from my latest position (on that folder), the positions of the folders reset when I close firefox, but now after some seconds it jumps to the top of the folder and each time I have to scroll down and open some links very fast and while I try to open as much link as l can, it jumps to the top of the folder, It waste my time and energy.

I have been dealing with an annoying problem after the latest update. I have some folders with multiple addresses on my "Bookmarks Toolbar" to check out some sites and accounts daily (Figure 1). Each folder contains more than one page (Figure 2) of bookmarks and I scroll down to open 10-12 addresses each time (Figure 2/3). Before the update, there wasn't any problem and when I came back to the folder I could continue from my latest position (on that folder), the positions of the folders reset when I close firefox, but now after some seconds it jumps to the top of the folder and each time I have to scroll down and open some links very fast and while I try to open as much link as l can, it jumps to the top of the folder, It waste my time and energy.
附加的畫面擷圖

所有回覆 (1)

more options

This issue with the bookmarks scrolling back to the top is a regression in Firefox 110 (bug 1809084) and This issue with the bookmarks scrolling back to the top is a regression in Firefox 110 (bug 1809084) and is being worked on.