Recently a bookmark was randomly deleted.
FireFox has been doing this for the last several version.
But, before, it wasn't much of a problem - I'd just do a restore from … (baca lebih lanjut)
Recently a bookmark was randomly deleted.
FireFox has been doing this for the last several version.
But, before, it wasn't much of a problem - I'd just do a restore from a bookmarks bu file that had the bookmark that had been deleted.
But not this time.
Clicked on the day I wanted, and got the usual warning that it would replace all the existing bookmarks.
But when it was run, it deleted all the bookmarks, but did not replace them with the ones from the bu file.
I then had _no_ bookmarks. There were none displayed, except for the star, something else I don't remember, and 'Other Bookmarks'. But clicking on these showed no content - they were empty.
At one point, and sometimes, a small window appeared saying 'Unable to process the backup file'.
But this was after the current bookmarks had been deleted.
I'm on 91.01, 64bit. I found other, earlier 9x versions, dl'd and installed them.
The attempt to restore bookmarks also failed running them
I then dl and installed a 89.x. But of course when I tried to run it, I got the warning about potential problems and the only choices to create a new profile or to exit. I chose to exit, and reinstalled the current version from a fresh dl.
After a few more attempts and system reboots, after the last reboot the current bookmarks reappeared, w.o. the deleted bookmark (as expected).
I have no idea why.
Bottom line: I can no longer depend on FireFox.
Fortunately, the deleted bookmark had relatively little content, so it can be recreated with 2 or 3 hours work.
But what happens when a bookmark with lots of content gets deleted?
I have bookmarks that have content going back at least 10 years.
There is no way I could recreate them.
Years of work would be lost.
I don't understand why, if the backup file couldn't be processed, the operation wasn't aborted w.o. making any changes. This is what a failed process should do by default.
I find myself incredulous that the FireFox development team let such an egregious bug slip through.
That's unacceptable.