Bookmarks
Starting yesterday, for some reason when I access my bookmarks, I have to start from the very top of all my lists of bookmarks. In the past when I accessed a bookmark, and then a clicked on the bookmark tab to access ANOTHER bookmark, my bookmark list would show where I had left off from the previous bookmark within that list.
Now when I access a another bookmark after I had accessed a previous bookmark, my bookmark list starts from the very top of it instead of where I was previously within that bookmark list. Being I have many bookmarks, (100's) it is a real pain to have to constantly scroll down from the top of my bookmark list every time to access another bookmark. I didn't have to do this previously. When I accessed bookmarks AFTER I accessed a given bookmark, the bookmark list stayed where I was previously located within my bookmark list. This made it easy to access my next bookmark selection! It sure is handy being all the hundreds of bookmarks I have, to have the list not ALWAYS revert back to the top of my bookmark list every time I want to find a bookmark!
This peculiar situation just started yesterday. In the past this would NOT happen when I accessed my bookmarks.
Looking at the bookmark manager and bookmark library I don't see options the change how the bookmark list is presented?
Can someone please help me and explain how do get back my old bookmark list actuation process? Thank you.
Krejt Përgjigjet (2)
This is a regression in Firefox 110 (bug 1809084).
- /questions/1404481 Bookmarks Menu List
Hi cor-el, thank you for your reply.
So, when I loaded the latest version of Firefox 110, I lost the bookmark list feature of staying at the present location I last selected, AND not going back to the top of the list and starting all over selecting a bookmark? Being I have hundreds of bookmarks, that new updated bookmark list feature is NOT a good feature!
I see if I hit Ctrl B, as you suggest, a bookmark sidebar appears, and the bookmark list acts as it did before by NOT reverting back to the top as it does now.
Is there going to be a fix with the latest Firefox update 110 to fix this problem, cor-el?
If not, frankly I'm tempted to revert back to Firefox 109 or whatever was the last version.
Thank you, cor-el, your help IS appreciated.