IndexedDB Error - gone after doing nothing

[Sopor]

After a reboot of my computer (Windows Update) I got the message IndexedDB Error and i opening the link and followed the instructions. I only verified that everything was correct. I can't see any reason why these settings should have changed because i haven't made any changes. When i got to step 7 i couldn't find any moz-extension+++ so i thought everything was lost but i open TSM and pressed the export session button and in the json file i could see my old URL's. I then pressed the TSM button again and instead off the message IndexedDB Error is not available in your browser i could now see my old sessions :)

I can see there have already been reports of the same issue but the strange thing is, i didn't do anything more than checking the folders and verified all the settings. I have no idea why it suddenly worked again.

Firefox 64.0 (64-bit)
TSM 3.1.0
Windows 8.1

[RobertAb1]

@Sopor- and others

Vote on Bug 944918, Bug 1423917, Bug 1541370, Bug 1482662, Bug 1546264, Bug 1427928 and other Firefox bugs listed here: #150 - to speed up this correction process including preparation of APIs by Mozilla and adding this future (and other ones) to TSM.

#150 - please, vote on all bugs on the list, so other problems with session managers can also be fixed; instruction on how to vote on Bugzilla can be found at the bottom of the list.

[Sopor]

I get the same error on every restart of Firefox.

Voted on all three :)

[RobertAb1]

@Sopor
Thanks!!! Can you vote also on other bugs on the list? There is a need for other few APIs/futures to be developed/fixed by Mozilla developers which are important for TSM development.

[Sopor]

I have now voted on all 49 bugs... I hope it was worth it :)

[RobertAb1]

Nice work!

Many of these bugs are related to:

• session management API,
• convert content-sessionStore to C++ (work needed to be finished before work on session management API can be done; this work will speed up session managers),
• ability to access/write back-forward history for each tab (mentioned by Sienori in 3 opened issues),
• improvement in tab discarding (solving problems with favicons),
• and more.

[1RonRock]

Is reinstating Favicons in the future plans? I really miss this feature, makes it so much easier to go back in a session to a previous tab.

[RobertAb1]

@1RonRock
I hope that reinstating favicons is in the Firefox developers' plans. Bug 1475240 was created by Shane Caraveo; he fixed earlier Bug 1378647, making possible for session managers to create natively tabs in discarded state. Bug 1475240, Bug 1450382, Bug 1462813 and Bug 1427928 are most likely the most important for favicons to function properly, but there is much more bugs related to discarding which can be found on voting list (link1, link2).

[1RonRock]

Time for me to vote. Thank you for bringing this voting ability to my attention.

[RobertAb1]

Please, also share links to voting list (link1, link2) everywhere (Firefox subreddit, GitHub, Discourse at Mozilla, Mozilla blogs and support pages, convince other session manager developers to post links to the voting list on their AMO pages, etc). Talk about new session manager options you need. Talk about problems that TSM has (broken indexedDB, etc), which are caused by errors in Firefox code and WebExtension APIs. Session manager developers can only do as much as WE APIs are allowing them to do.