Forum Discussion
josh_bodner
Oct 15, 2020Former Employee
Dev channel update to 87.0.664.8 is live
Hello Insiders! Today we’re releasing build 87.0.664.8 to the Dev channel. This is the last build for major version 87, so except for maybe a small patch or two, this is the build that will soon be...
josh_bodner
Oct 16, 2020Former Employee
MikeDiack In this case, the bug is actually fixed! It's the way we fixed it that caused the same thing to happen. Basically, we were trying to merge some code in from Chromium, and that changed the storage for the current session, which was the first time peoples' tabs were lost. Unfortunately, we couldn't leave the code as it was, and the safest way to fix it was to just undo those changes, which in the process changed the storage again, which was the second time peoples' tabs were lost.
In the meantime, we've also identified an issue where peoples' sessions weren't written to storage for history, which is what's affecting the people who can't restore their windows from history because they aren't there.
Colm O Brogain
Oct 18, 2020Copper Contributor
Don't ever, ever, let that happen again. It's inexcusable to KNOW you are going to blow away people's session and just do it anyway. Save open tabs to bookmarks in a folder, do SOMETHING.