-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chrome doesn't respect the autocomplete property of the p-autocomplete component #8096
Labels
Type: Bug
Issue contains a bug related to a specific component. Something about the component is not working
Milestone
Comments
Merged
+1 |
5 similar comments
+1 |
+1 |
+1 |
+1 |
+1 |
yigitfindikli
added
the
Type: Bug
Issue contains a bug related to a specific component. Something about the component is not working
label
Oct 3, 2019
Fixed in f539e1b |
I think I have a solution for autocomplete, since it still doesn't work. As of 2018, you have to change autocomplete="new-password" instead of autocomplete="off" for it to work (autocomplete="off" doesn't work any more). Checked it, changed it in my project and it works. Hope you will fix this soon |
Still not fixed, prime-ng 11.4.2 |
+1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Type: Bug
Issue contains a bug related to a specific component. Something about the component is not working
Current behavior
The p-autocomplete component has the autocomplete attribute set to off by default. However, even with this value, Google Chrome's autocompletion is still displayed, causing the problem shown in the third image (Chrome's autocompletion appears over the component list).
Expected behavior
The expected behavior is Google Chrome's autocompletion not being displayed, but after some research, I found out that Chrome ignores the autocomplete property when it is set to "off".
To fix this, I created a new @input in the p-autocomplete component and associated the autocomplete HTML property with it, in a way that the developer is able to send a value that actually disables Chrome's autocompletion.
Please take a look at PR #8097
References:
https://stackoverflow.com/questions/15738259/disabling-chrome-autofill
https://bugs.chromium.org/p/chromium/issues/detail?id=370363#c7
Angular version: 7.X
PrimeNG version: 7.X
Browser: [Chrome]
Language: [all]
The text was updated successfully, but these errors were encountered: