[DELETE UNANSWERED CLOSED POSTS] Password suggestions don't match domain or username when username is pre-filled

On my PC, the password suggestion list suggests every password from every domain when the username field is automatically pre-filled, instead of the saved password for the username.

When I delete one character, it correctly suggests the matching name and password.

In the little info-bit of your Original Post, above, you wrote:

“Linux Mint Una 20, Brave Version 1.68.128 Chromium: 127.0.6533.73 (Official Build) (64-bit)”

Brave Support needs to know the most recent version of Brave Browser that you are now using.

Please edit/fix up your Original Post and attempt to follow the Brave Support guidelines for submitting a bug report (Official Brave Help Center article):

https://support.brave.com/hc/en-us/articles/360018228951-How-do-I-submit-a-bug-report-

My own suggestions for how to create a bug report, wherein I provide some examples of the steps to take:

How to create a Bug Report


Regarding your description of the issue; maybe write that as:

On my Linux OS PC, the Brave Browser’s Password Manager’s password suggestion list, suggests:

  • every password from every domain when the username field is automatically pre-filled

  • instead of the saved password for the username.

Writing that, helps the readers of your post, more clearly see the details of your post (IMHO).

And, if you can, change the title of your OP, to only:

Password suggestions don’t match domain or username when username is pre-filled


Hello,

This was posted before a skeleton template was introduced to better guide reports.

I am now using Version 1.78.102 Chromium: 136.0.7103.113 (Official Build) (64-bit)

On my Linux OS PC, the Brave Browser’s Password Manager’s password suggestion list, suggests:

  • every username from every domain when the field is empty;
  • every password from every domain when the username field is automatically pre-filled;
  • instead of the saved password for the username.

The bug is still present.

Do we know if Brave differentiates between subdomains when suggesting saved logins?

I understand that in a free text interface, people can choose whichever words they deem appropriate or best describes their issue and makes sense to them, however inaccurate or unsuitable they may appear to others. I suppose it depends on what words existing/new members choose. Normalisation of reporting terms would help by providing relevant normalised entries to expedite reporting, avoid embarrassment and reduce errors.

The template was s step towards formatting reports and making them easier to search through. I see scope for further improvements.

If there is a specific terminology for a specific features, it should probably be made known when reporting.

When I search issues, or web sites, I use as many different ways as possible but still can’t guarantee it matches what some people have described.

I wonder how many bugs are left because of mismatched communication ideals.

To clarify, are you saying that the behavior you’re expecting is that when you land on a login page, the username and passwords are pre-filled in the login fields? Additionally, you’re saying that the behavior that you do see is that those fields are not filled and instead, when you click in them, are shown suggestions from the entirety of your pw list, rather than just the ones for the domain you’re on?