Hi,

The people who answer questions here, for the most part, are other Firefox users volunteering their time (like me), not Mozilla employees or Firefox developers.

If you want to leave feedback for Firefox developers, you can go to the Firefox Help menu and select Submit Feedback... or use this link. Your feedback gets collected by a team of people who read it and gather data about the most common issues.

You can hide the screenshot image with code in userChrome.css.

See:

• [/questions/1235026#answer-1157834] "New Bookmark" panel too big; any user-side way to size it down?

whatnot said

and then - in case you forgot what you just did a second a go - you are reminded that it was 'saved to Library!' oh yeah? do you take your users for idiots?

Firefox 62 changed from saving a bookmark automatically -- even if you pressed the Esc key in that panel -- to saving a bookmark if you click Done or if you let the panel time out. Perhaps the UX designers felt that users needed more than just the star being blue or not blue to communicate the new behavior?

Since these confirmations are new, I suggest not hiding them until we learn more about what else they will be used for.

jscher2000 said

Perhaps the UX designers felt that users needed more than just the star being blue or not blue to communicate the new behavior?

perhaps they should have asked first? they wheel out these useless gimmicky updates as if they're doing us a favour.

they don't seem to be familiar with the concept of 'optional' either.

cor-el said

You can hide the screenshot image with code in userChrome.css. See:

• [/questions/1235026#answer-1157834] "New Bookmark" panel too big; any user-side way to size it down?

frankly, I'd rather roll back to the previous version.

whatnot said

jscher2000 said

Perhaps the UX designers felt that users needed more than just the star being blue or not blue to communicate the new behavior?

perhaps they should have asked first?

Most significant UI changes are tested with users.

jscher2000 said

Most significant UI changes are tested with users.

this might not be 'significant', in the grand scheme of things, but it's none the less annoying, and adds nothing to user experience - why not focus on security and stability and leave such cosmetic changes optional?

also, asking to test something they think you need is not the same as asking you if you actually need it. why waste time and resources to come up with these redundant 'solutions' to imaginary problems.

but maybe I'm mistaken, maybe this is the new global standard of bookmarking process which will revolutionise the experience for generations ahead.

Hi whatnot, since you like posting on this site, why not pitch in and answer some user questions?