Inability to disable all kinds of autocompletion on a text field
Reported by
a...@codeart.us,
Jan 3 2018
|
||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.84 Safari/537.36 Steps to reproduce the problem: 1. Add autocomplete="off" 2. Observe autocompletion still happens What is the expected behavior? Autocompletion should be disabled with autocomplete="off", like other browsers do this. Not with "false" or any other hacks/tricks, like "new-password". This is not a password field. What went wrong? We do use libraries that replace regular <select> with a customizable drop-down allowing users to search and use AJAX to dynamically load list options (useful for large lists). The library provides a text field where users can type a query, see the screenshot attached – a double drop-down displayed with no way for us to disable autocompletion for this field. The content of this field is not submitted to the web server, the field doesn't even have a name attribute, so forcing autocompletion on such fields is nonsense. Did this work before? Yes Does this work in other browsers? Yes Chrome version: 63.0.3239.84 Channel: n/a OS Version: OS X 10.13.2 Flash Version:
,
Jan 4 2018
Thanks for filing the issue. @Reporter: Could you please share a sample test File/Web URL which helps us in triage the issue. Can you please provide the screencast of the excepted behaviour of the issue reporter which helps us in better understanding it. Any further inputs from your end may help us. Thanks!
,
Jan 4 2018
,
Jan 4 2018
Hi, I only have that screenshot from one of our users. So far I can't reproduce this on my end. Attached screenshot displays the expected behavior. Will ask for the exact browser version.
,
Jan 4 2018
Thank you for providing more feedback. Adding requester "sc00335628@techmahindra.com" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 4 2018
[mac bug triage]
,
Jan 5 2018
As per comment#4 from the reporter adding the Needs-Feedback label
,
Jan 5 2018
,
Jan 8 2018
,
Jan 12 2018
I can reproduce this in 63.0.3239.132, running on Arch Linux
,
Feb 21 2018
This is strictly related to https://bugs.chromium.org/p/chromium/issues/detail?id=587466 (where many developers spent a lot of time describing why Chome should respect the autocomplete=off attribute, uselessly)
,
Feb 23 2018
Images speak louder than words (hopefully). This is why developers (and Google itself) need autocomplete="off" to be respected by browsers:
,
Feb 23 2018
You can reproduce the issue here: https://developers.google.com/maps/documentation/javascript/examples/places-autocomplete-addressform
,
Mar 21 2018
Mac triage: marking for Autofill triage and widening OS flags.
,
Apr 23 2018
Mac triage: to mathp@ and estade@ directly for autofill triage. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by krajshree@chromium.org
, Jan 3 2018