Hello @mike17, @J805.
This happens because input passwords by default, as mentioned by you guys, have
So the browsers / passwords managers / extensions (…whatever…) Interpret that field it’s a sign-up one, and that’s why they suggest a new password even if the field it’s used for a login purposes.
Bubble could offer a dropdown in the input properties with election type: (sign up field or login field) and changing the
autocomplete type depending on the election.
As you can see here:
"autocomplete" attribute has multiple possible choices. The one we’re looking for, would be:
autocomplete="current-password" ⇾ This attribute value will indicate to the browser (or whatever we are using as password manager), that field is a password field that doesn’t need any “new password” suggestion.
This should be pretty easy, we just need to overwrite the
"autocomplete" attribute for the specific field using JS.
(In the left input the browser suggest a strong (new) password, while in the right it only suggests saved passwords).
Demo: Bubble | No-code apps
Editor: Anti-dup | Bubble Editor
@J805 I don’t think this could be “listed as bug”, but looks a good feature to submit in the Ideaboard