RochDoug said

By "located on the first line", I meant that I considered the possibility that Firefox truncated longer content, but the parts I really needed (like user names) were always located at the very beginning of longer content.

Okay, I was confused by the word subsequent.

So for some items the beginning of the Description was missing? That's very difficult to explain. Does my converter tool give any different result?

Haven't tried the converter tool yet.

How to get 'er back. First off Mozilla is going the way of Microsoft and doing it their way and not how you want it. To get back you "properties" with all the remarks in them you will have to go backwards. I just did this the other day when I found more complaints. The version you will end up with is 60.2.0esr (extended service release) which is for corporations that can't upgrade all the time. If you go to: https://www.mozilla.org/en-US/firefox/organizations/all/ pick you language and operating system, download the file (it should say firefox setup 60.2.0esr) and then install it. I didn't even have to delete the 62.0 as it installed right over it. I have my properties back with all the notes still in them. Mozilla may not like this reply and delete it. Hope it helps you as it worked for me.

Thank you for the esr link. That did the trick.

Someone mentioned that the removal of the description feature was mentioned in release notes. I don't always check those because much of the time, the information is rather cryptic and of interest only to programmers. But for this feature, Mozilla should have found a way to notify users that they were about to (apparently) lose data and waste precious time finding it again. As you said, "going the way of Microsoft". It's inexcusable.

This is a really stupid "solution." It used to be that I could find my Properties notes simply. Now I have to open the HTML file. You people are really, really dumb when it comes to "updating" and "improving" stuff for those of us who have been faithful Firefox users FOR YEARS. I will be looking for a better browser. GFY.

In addition, individual website sometimes require one to update one's password info, for whatever reason. It used to be that one could do so, and then, quickly, change the coded info saved in Properties's notes section. NOW, one has to: (1) change the password for the website; then (2) re-export the entire bookmarks file to rewrite the entire old bookmarks file, to save one or two keystrokes in one password setting. This is, as I say, stupid beyond belief.

purefog, just read a couple of posts above your's. It's easy.

Hi purefog, there are many more secure ways to store logins than Bookmark descriptions. I realize you are used to that way, but you have a lot of other choices.

RochDoug said

Someone mentioned that the removal of the description feature was mentioned in release notes. I don't always check those because much of the time, the information is rather cryptic and of interest only to programmers. But for this feature, Mozilla should have found a way to notify users that they were about to (apparently) lose data and waste precious time finding it again...

This has and will continue to frustrate a number of users for long time who use this part of the Bookmarks.

I read where the Description feature in the Bookmarks was used only by a tiny percentage of users. I guess there's data going back to them about detail browser usage. I guess 'we' complaining here are only a slight fraction of the tiny fraction of Description users.

So, there's no Extension Bookmark to 'take over' and have Descriptions intact, I suppose?

~Pj

This may be a symptom of the decline of good program design which has been going on for quite some time. It reminds of when Netscape's crew decided it was fun to be pathetic, so they wrecked the bookmark search feature, and legions of devotees (mostly programmers, some of whom were likely the guilty parties) defended the error as if someone had dissed their mothers. Somehow, the broken search feature landed in Firefox and it persists to this day.

Carrying on the tradition, Google seems to think it's amusing to release app and OS updates without consulting any users or testing the code. Witness the battery charging issues with some Pixel phones since the Pie update.

In many cases, programming skills aren't the problem. It's the design aspect which has fallen apart. Software producers seem to be skipping a few steps and letting programmers design user interfaces and choose features. That's not always a good idea. See "Exploring Requirements - Quality Before Design" by Donald C. Gause & Gerald M. Weinberg.