lost container information when I diconnected sync and deleted saved data
OK I was tidying up my bookmarks that over the years through various iterations of Firefox /chrome. But first I disconnected from sync and elected to delete all the saved sync information. I then went through and tidied all my book marks getting rid of any duplicates and ones with broken links. All good. Next I closed everything down and restarted. Had all my bookmarks just how I wanted them. Reconnected to my Firefox account to update all the saved data from my machine to account. Went away to allow time to sync. Closed Firefox after an hour or so. Open Firefox and automatically connected to my Firefox account. All the bookmarks are there as I had left them. No problem. Firefox seemed to delete all the browsing history (or maybe it didn't sync it in the first place). BUT.....no container data. It has reset the containers to the default state. Pretty sure this is not how sync should work. but when I open a private browser its container data seems to be intact. Anyone struck this? I notice Firefox updated to 66 on 19/3/2019 Love containers, its close to what the internet should be like I know container data has not yet been made part of sync (everyone wants it!) but is this a bug or something they forgot to tell us in the new release. EDIT Bit more information. websites will not open in new container. Firefox gives prompt to always open in xxx container but then simply hangs
由 berniek 於 修改
Clearing all the history data made it work again as it should. Maybe it has something to do with where the container data is held.
Premature answer above. Still broken. Some websites open in their own containers but some just get to the "open in xxx containers" page and no matter what is selected just hangs.
Well it appears to be something to do with the mouse clicks. It will move the focus OK, it will tick & un tick the box but it seems to only generate a "enter" very spasmodically. However the keyboard enter seems to make it work every time. Looking more and more like a bug when going to version 66 (and the move to database to hold preferences?). Setting the processes back to 4 does not fix it. Once I hit return on the keyboard it all works as it should forever more. It seems to be only on saving the preferences for the website/container that this fails.