Autofill don't validate Component on Chromium browsers
See original GitHub issueDescribe the bug
On Chrome/Edge (and maybe Safari), when using Autofill to fill the component inputs, adyenCheckout state.isValid
remains at false
and in state.valid
, these fields are missing:
- encryptedCardNumber
- encryptedExpiryMonth
- encryptedExpiryYear
- encryptedSecurityCode
This bug doesn’t occur on Firefox.
To Reproduce Steps to reproduce the behavior:
- Load adyen form in Chrome
- Autofill fields with a saved card
Expected behavior
Inputs are filled and state.isValid
should be true
Screenshots
Desktop (please complete the following information):
- OS: Ubuntu
- Browser: Chrome
- Version 106.0.5249.103
Issue Analytics
- State:
- Created a year ago
- Reactions:3
- Comments:7 (2 by maintainers)
Top Results From Across the Web
352347 - Don't autofill passwords where confirmation is required
In this situation, Chromium shouldn't be filling into this particular field. Filling any password field preceded by a text input is being too...
Read more >bug(input): Chrome autofill should set the form to valid #3414
So I've found that the main issue here is that Angular's RequiredValidator doesn't acknowledge inputs with autofilled input before the user has ...
Read more >How do you disable browser autocomplete on web form field ...
The solution for Chrome is to add autocomplete="new-password" to the input type password.
Read more >Autofill: What web devs should know, but don't - Cloud Four
Auto-Fill Credit Card Forms Using Your iPhone's Camera in iOS 8. ... audiences to raise their hands if autofill is part of their...
Read more >Autofill - web.dev
On the sign-in form, you can use autocomplete="current-password" to tell browsers to offer the option to fill in previously saved passwords for this...
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 FreeTop 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
Top GitHub Comments
We use the latest version, whatever that is, and also experienced this on 4.x. This is really hurting our business, so please fix asap.
Hello,
Autofill is working on the demo https://www.mystoredemo.io/ but still not on our website. And i use Chrome 106.
Like i said in the first post, in the
onChange
event,valid
doesn’t add encryptedCardNumber, encryptedExpiryMonth, encryptedExpiryYear and encryptedSecurityCode when using autofill on Chrome. But it is working correctly on Firefox.