You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I do use Firefox with the "Delete cookies and site data when Firefox is closed" option.
When I open Firefox again and navigate to my GB instance or to https://latest.glowing-bear.org/, all settings are "back to the default" which is to expect, typically the "Only show buffers with unread messages" is back as its default to "False", meaning I see many many buffers with no unread messages.
BUT when I open the setting panel my old options are still here: "Only show buffers with unread messages" is checked! I have to uncheck it and check it again to see the buffers with no unread messages dissapear.
The text was updated successfully, but these errors were encountered:
Not quite sure how this could happen - while we don't watch for changes in localstorage, they are reflected after a reload. And we certainly can't know about values that were deleted between browser restarts. I just tried this in Firefox - manually modifying a setting and reloading GB caused the setting to be applied.
Interesting. Wouldn't that be more of a Firefox bug then? I don't understand how this could happen, but it's also been years since I was properly familiar with the GB code base to be honest...
I do use Firefox with the "Delete cookies and site data when Firefox is closed" option.
When I open Firefox again and navigate to my GB instance or to https://latest.glowing-bear.org/, all settings are "back to the default" which is to expect, typically the "Only show buffers with unread messages" is back as its default to "False", meaning I see many many buffers with no unread messages.
BUT when I open the setting panel my old options are still here: "Only show buffers with unread messages" is checked! I have to uncheck it and check it again to see the buffers with no unread messages dissapear.
The text was updated successfully, but these errors were encountered: