2025.1.0 / 2025.2.0 Browser Extension UI/UX Megathread

Like the new enhancements to Chrome extension but would like to see:

  1. one Click edit button to edit saved items as opposed to view->edit

  2. one Click feedback somewhere prominent in chrome extension

@Peter_Ruchkin Welcome to the forum!

I moved your post into this “feedback thread” to the new UI/UX.

Your first point was mentioned more than once - but as far as I see, there is no Feature Request for it, yet.

To your second point: What exactly do you mean by “one Click feedback”?

Thank you.

A button on the extension to submit feedback

So, one feedback-button to submit general feedback about the browser extension?

@Peter_Ruchkin I just created a Feature Request - though not for a one-click-edit-button - but for an “Edit”-entry in the item menu (I think a button is also a good idea, but another extra button would add to the problem of “space”, especially in “default width” of the extension… maybe another feature request from someone…):

When can we expect an improved version of the browser extension? The UI and UX are terrible. It’s one big mess of different fonts, elements, etc. The extension used to be fine.

Hey @Gerben1 can you share more detail on what you are hoping to see? You can configure your autofill experience as needed.

I’d like to refer to the hundreds of remarks in the other topic.

The team has iterated on the experience since the redesign, but don’t hesitate to share more detail on what you are hoping to see specifically so that we can pass it along to the team.

In the newest version of the extension on Firefox (2025.5.0), the main UI jank that still exists is the loading circle when opening the extension, it starts off as a big circle then becomes a smaller circle then the whole UI flashes in. This is more noticeable if it takes longer to load but is always there. Would be a lot better if the loading circle didn’t display at all for super fast loads, and when it did display, if it stayed fixed in one position and size, or if you used React-style loading placeholders instead. Just looks unpolished at the moment.