Issue metadata
Sign in to add a comment
|
Autofill not responsive to developer direction
Reported by
tbut...@gorout.com,
Sep 12
|
||||||||||||||||||||
Issue description
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.81 Safari/537.36
Steps to reproduce the problem:
1. Build a form
2. Indicate autocomplete="off" or randomize the form name, id and/or the autocomplete value
3. Attempt to add data to a form field
4. Go crazy for no reason!
What is the expected behavior?
If autocomplete="off" is specified or autocomplete="{random value}" is specified auto-fill suggestions should not be presented... Chrome should not insist on auto-filling the form field with suggested values.
What went wrong?
No matter what is attempted or however many coding hours we spend to prevent auto-filling form fields, Chrome insists on providing auto-fill suggestions.
Did this work before? Yes Chrome 68
Chrome version: 69.0.3497.81 Channel: n/a
OS Version: 10.0
Flash Version:
Google/Chrome should not be trying to maintain such extreme control over autocomplete and auto-fill settings! Why do you do this? What is the purpose?! If a developer wishes - FOR ANY REASON - to disable the autocomplete and features of any field or an entire form, it should be overridden... period!
There are several (if not hundreds) of situations or development scenarios where autocomplete and auto-fill is not appropriate. In some cases, this behavior invalidates form entries that are expected to be unique each time the form is submitted. In others, it may present security risks by prompting previously entered data that may be sensitive or applied incorrectly.
In any event, this behavior should be in the hands of the developer and controlled via HTML or through JavaScript. It defies explanation that Chrome continues to ignore developers on this issue.
Last month our team spent several developer hours applying a workaround that successfully disabled autocomplete and auto-fill on our application's forms. Now, with the release of Chrome 69, autocomplete and auto-fill is back and it ignores our workaround completely. This is maddening!!
PLEASE STOP IGNORING ALL DEVELOPERS AND ADDRESS THIS ISSUE!!!!
,
Sep 12
The login screen here should provide a good example of this behavior: https://dev.gorout.net/
,
Sep 12
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 13
,
Sep 13
Hi, A simple example of page where autocomplete is making filling form a lot more difficult: 1) Registering new users to application by call center - a new data (like user name, email etc.) have to be provided each time the form is being filled by CC user. 2) Inputs where autocomplete is implemented on JS side (like in Jira, when You are defining asignee to the issue - it (as-you-type) suggest users that have account in Jira, however Chorme show's his autocomplete suggestions which ruins the functionality of Jira) 3) I had problem even with component delivered by Google itself - the Google Maps Location Autocomplete (JavaScript) which also provides suggestions by itself which were ovelapped by Chrome autocomplete Summarizing: Chrome should provide a clear working solution for developers, so they can disable autocomplete in cases like described above, without fear of new version of Chrome ruining they effort.
,
Sep 13
,
Sep 25
tbutler@ - Thanks for filing the issue...!! Could you please provide a sample test credentials for the url at comment #2. This will help us in triaging the issue further. Thanks...!!
,
Oct 4
Happen also on Chrome 69 on MacOS 10.14. It should be on priority 2, as a web developer is very annoying and can destroy the howl design of the website.
,
Oct 4
*priority 1 And it also happen in Chrome canary on MacOS. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by rtoy@chromium.org
, Sep 12Labels: Needs-Feedback