(React) UI Components don't support password managers
See original GitHub issueDescribe the bug Browsers don’t recognize the input elements as Auth related.
-> No “password suggestion” on during account creation -> No autofill during sign in -> No prompt “save password?” during sign in
I’m not sure what details are necessary for this to work, but I tried setting the name
attribute and others through formFields
. But that didn’t help solve this issue. (https://www.chromium.org/developers/design-documents/form-styles-that-chromium-understands)
-> Form is not part of a “form” element -> The “sign in/up” buttons aren’t labelled as type “submit”
Issue Analytics
- State:
- Created 3 years ago
- Reactions:44
- Comments:52 (20 by maintainers)
Top Results From Across the Web
Should You use Controlled Components for Passwords in ...
The answer to our question — should we use controlled components to manage passwords in React? — is yes. While an input element...
Read more >PasswordField | Amplify UI for React
PasswordField allows users to input passwords with the convenience of full password manager support.
Read more >Why Users (Don't) Use Password Managers at a Large ...
Abstract. We quantitatively investigated the current state of Password. Manager (PM) usage and general password habits at a large,.
Read more >Making password managers play ball with your login form
Password managers are built to work with all login forms that follow best ... as it has no browser support), to make sure...
Read more >react material Ui textfield type password disable autofill from ...
have you tried <form autocomplete="off">? – Jatin Parmar. Apr 11 at 17:42 · I dont have form tag over my component. – tyler....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Personally, I don’t think this should be labeled as a feature-request, this is a bug. Users are really confused about this.
Currently, there is no point in using the password component.
This is a blocker for us (and probably most people) to upgrade our version of Amplify without a workaround. Looks like this bug seems to have been there for a while, any news on when it will be fixed?