Potential Bug in Chrome - Clicking Bookmark Bar Folders Opening the Wrong Folder

[balthanon]

So I'm not actually sure this is a Floccus bug or if I just have something corrupted in my Chrome profile or if it is more on Chrome's end. I've been running into an issue lately where after the browser has been open for awhile (typically overnight, potentially with a sleep cycle), clicking on a folder will open another folder in my bookmarks. So as an example, in the image below, clicking the reading folder will open all bookmarks or roleplaying.

While troubleshooting and disabling extensions, disabling Floccus fixed it once, but not another time, so I suspect it was just reloading the browser and pulling bookmarks from local storage that did it. Forcing a sync with Floccus also resolved it.

Could anyone try adding several folders to their Chrome bookmarks bar and see if they have similar behavior? If so, I'll go ahead and create a bug. (Or if Marcel wants this as a bug before hand I can transfer it now.)

[marcelklehr]

Hi @balthanon
I'm sorry to hear you have trouble again :/

clicking the reading folder will open all bookmarks or roleplaying

Mmmh, do you mean

"when I click the item representing the reading folder, it will open a toolbar underneath the item representing the roleplaying folder displaying the contents of the roleplaying folder as if I had clicked on the item representing the roleplaying folder"

or do you mean

"when I click the item representing the reading folder, it will open a toolbar underneath the reading folder item with the contents of the roleplaying folder"

ie. is it a case of visual click location / reaction location mismatch? or a case of the folder contents appear in a folder where they shouldn't appear?

Neither has happened to me before.

[balthanon]

Thanks.

The first example is what's happening-- clicking the reading folder is acting as if I clicked the reading folder or all bookmarks, with the toolbar opening in that location. Sounds like this is probably something Chrome profile related or something then if you haven't seen it and have the same set up-- possibly tied to touch too, I might have only seen it on my Surface Pro now that I think about it. It's the only computer I use Chrome on as a primary browser.

[marcelklehr]

Ah, yes, that sounds more like a chrome issue indeed.

[balthanon]

Closing this-- I replicated this issue on Edge without floccus installed; so definitively not tied to syncing.