hello, websites are not and were never able to read your firefox bookmarks - there is no such API in firefox, which can be independently verified as all the source code is open and freely available.

this was never mozilla's explanation for why the description section for bookmarks got removed either - that was done for performance reasons and removing complexity (bug 1402890).

Yeah you say that now. Back when it happened, story was different.

The "story" then was the same as it is now -- all annotations in the places.sqlite file were slated for removal, in stages as the "surviving" features were re-written for performance. Basically an update of the places.sqlite features 10 years into the "Places" database system.

All places.sqlite actions were previously synchronous and done in the main Firefox processor thread and this affects the responsiveness of Firefox. All actions are now done asynchronously in their own processor thread, not only for places.sqlite database actions, but also for all other components. The description field hasn't made it to the new asynchronous version for various reasons. The description field was only exposed in the Library and there was already another description field available used for the new tab page that was filled via the meta tag on the website.

Never had any performance issues with firefox in the past even with ton of bookmarks. Like i said, back when it happened, the word was not performance ut security related problem. Sites reading bookmark comments problem.

Descriptions are a minor feature of bookmarks Marco Bonardo said Really  ? Description was the BIGGEST feature of bookmarks. People put notes there and login info and passwords. And now its gone (well not now)

Type: enhancement Really ? enhancement ? Since when taking something AWAY is an enhancement ? Try male enhancement pills. Will you be happy if it makes it smaller ?

Where is logic in here ?

Then Marco Bonardo suggests to use web extension instead ? Thats allot safer right ? RIGHT !!!!!!! (what an #####)

Regardless of what the explanation was and is, this is more a case of the developers deciding that they know what the users want better than the users themselves, implementing whatever they want. breaking functionality for many users with every new major release, and being 100% non-responsive to complaints from the users that they created problems for.

Case in point: Prior to FF69, there was a setting that allowed Firefox to remember your decision on the use of Adobe Flash on any given site. Then they removed that setting, citing the upcoming deprecation of Flash as justification ... even though that isn't going to happen until the beginning of 2021. Because every website that uses Flash is on their own internal timetable to replace it with whatever is appropriate in HTML5, this means every time I access a site that hasn't upgraded yet, I have to authorize Firefox to run Flash via the pull-down from the address bar. EVERY SINGLE TIME.

It happens that there are four sites I visit daily, in order to play Hidato, Sudoku, Jumble, and the like. I have been visiting those sites for literally years. They pose no security threat, yet they are probably going to be staying in Flash until almost the last minute, because those online puzzles are going to be difficult to replicate in HTML5. I have asked -- multiple times -- for a relatively simple fix, which is to modify the pull-down to allow Firefox to "remember" my decision to allow only for that site.

All I get in return is "we did this because Flash is going away" ... well, yes, I have acknowledged that every time. But they acted more than a year before that was going to be an issue, they have inconvenienced every user who has a circumstance like mine, and now we are at FF72 and guess what still hasn't been addressed by them.

I'm going to keep complaining about this until either they put in a temporary fix (which, of course, would be removed along with Flash support itself a year from now) or time runs out. I figure that if they can't be responsive, they deserve to be called out on it as often as they put out a release that doesn't address this simple, basic problem which they created and now apparently refuse to fix.

Corrupt? Only in the sense that the developers seem to have a collective God syndrome.

There is a way to allow Flash on specific domains by using a policies.json file. This works only for the curent session, so you need to repeat after closing and restarting Firefox

• /questions/1268957 Adobe flash will not remain active on our 24h emergency medical web site

See:

• https://github.com/mozilla/policy-templates/blob/master/README.md#flashplugin

Anything that isn't automatic every time I launch Firefox is not a solution for me. (Probably not for the vast majority of us.)

But thanks for trying.