Autofill does not respect autocomplete="off"
Reported by
j...@squareup.com,
Dec 12
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36 Steps to reproduce the problem: 1. Create a form input with autocomplete="off" 2. Focus on field 3. Autocomplete will still try and fill the field What is the expected behavior? Respect the HTML attribute autocomplete="off" and not display the autocomplete dropdown. What went wrong? Autocomplete covers the existing dropdown for customer selection. Did this work before? Yes Unknown. Chrome version: 70.0.3538.77 Channel: n/a OS Version: OS X 10.13.6 Flash Version: There is a similar bug from 2014 that was marked as "Won't Fix". This really needs to be fixed as you can see from the attached screenshot.
,
Dec 12
This is so necessary
,
Dec 12
There is also this survey of valid use cases for autocomplete="off" that never received followup: https://bugs.chromium.org/p/chromium/issues/detail?id=587466&can=2&start=0&num=100&q=&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Component%20Status%20Owner%20Summary%20OS%20Modified&groupby=&sort=
,
Dec 12
This bug is also directly related as we encounter the same issue when implementing our terminal on the web: https://bugs.chromium.org/p/chromium/issues/detail?id=55719
,
Dec 12
This bug is also related as Chrome should not be filling out hidden fields: https://bugs.chromium.org/p/chromium/issues/detail?id=132135
,
Dec 12
This bug is also related, again, hidden fields should not be filled: https://bugs.chromium.org/p/chromium/issues/detail?id=448539&q=Autofill%20&sort=-stars&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Component%20Status%20Owner%20Summary%20OS%20Modified
,
Dec 12
To highlight the impact of this issue, there are at least 5 issues tracking side effects of the decision to not respect autocomplete="off". Those issues collectively have 333 stars, not including the 18 for this ticket. Collectively, that would make this is the 17th most starred issue currently open in Chromium. The StackOverflow post (https://stackoverflow.com/questions/15738259/disabling-chrome-autofill) tracking workarounds has 620 upvotes and 189 stars, and the top response 629 upvotes. The first page of responses collectively have over 1000 upvotes. It has been viewed 427,817 times as of 12/12/18.
,
Dec 12
,
Dec 14
Able to reproduce the issue on Win 10, Mac 14.2 and Ubuntu using Canary #73.0.3639.0, Dev 72.0.3626.14, Beta 72.0.3626.17 and Stable 71.0.3578.98 using https://www.w3schools.com/code/tryit.asp?filename=FY7683X7YLZR Issue existing from M34 version. Requesting Dev team to check the issue and update accordingly.
,
Dec 27
This is breaking the user experience exceptionally, specially where there are auto suggest feature to select user input from dynamic list of data like selecting city of journey. In such cases there are two auto suggest popup are coming.
,
Jan 15
Very annoying bug. It causes problems for our website in two major cases: 1) on administration area pages. When customer care rep. enters city, address, email or other information, it is usually NOT his own address but user's address. I want to completely turn autosuggest\autocomplete off, for individual field or entire form. 2) with custom autosuggest lists. In this case two lists are shown, see screenshort. It's not clear for me, why Chrome decides to show autosuggest, while web developer explicitly says "turn it off for this field!" |
|||
►
Sign in to add a comment |
|||
Comment 1 by j...@squareup.com
, Dec 12