Issue metadata
Sign in to add a comment
|
Chrome for Android does not honor autocorrect input attribute
Reported by
gk.jo...@gmail.com,
Nov 5
|
||||||||||||||||||||
Issue descriptionSteps to reproduce the problem: 1. Open https://output.jsbin.com/qacoforama/3?output in mobile Chrome 2. Try to type something in the input field 3. You will see keyboard suggestions What is the expected behavior? You should not see any suggestions, because "autocorrect" attribute on input field set at "off" What went wrong? One picture with suggestions is Chrome, and another one without suggestions is Safari Did this work before? Yes It initially started to work in Chrome 38, can't say about other versions and when it became broken Does this work in other browsers? No 1) Mobile Safari There is no such problem in mobile Safari. The keyboard does not provide any suggestions when autocorrect="off" 2) Mobile Firefox The same problem as in Chrome: autocorrect="off" does not work, so one can see some suggested words Chrome version: 70.0.3538.80 Channel: stable OS Version: 7.0 Flash Version: There is an old issue where the same problem was described https://bugs.chromium.org/p/chromium/issues/detail?id=303883. As a result the issue was resolved and autocorrect="off" was honored. But at some moment it was broken and still does not work.
,
Nov 6
Tested the issue on android and able to reproduce the issue Steps to reproduce: -------------------------- 1. Launched chrome and navigated to https://output.jsbin.com/qacoforama/3?output 2. Now clicked inside input field and observing keyboard suggestions as shown in screenshot Chrome version: 60.0.3112.113, 70.0.3538.80 , 72.0.3601.0 OS: Android 9.0 Android device: Pixel 2 XL This issue is seen from older M-60 builds, hence considering this issue as Non-Regression and marking as Untriaged for further triaging. Also cc'ing owner bcwhite@ from similar issue https://bugs.chromium.org/p/chromium/issues/detail?id=303883 for further inputs. Thanks!
,
Nov 8
Changwan, can you route this to the correct team/person?
,
Nov 8
This is working as intended. You need to set 'autocomplete=off' to prevent this.
,
Nov 8
My bad, I only checked the description. Would it be fair to say that autocomplete attribute isn't working correctly, then?
,
Nov 8
I don't think so. From my point of view, autocomplete feature provides to a user just previously submitted values (through this input field).
I've attached a picture with an example of autocomplete. You can see "Yyy" and "Hhh" values that I submitted a little earlier using this input.
And this behavior is controlled by "autocomplete" attribute. When "autocomplete" is "off", you will not see previous values.
At the same time one can notice that the keyboard provides its own suggestions ("What", "I", "You"). And they are not connected with previously submitted through the input values. They are like predictive and the keyboard tries to guess what you most probably want to type right now.
The keyboard works exactly the same in other applications. I've attached a screenshot with note-taking application where the keyboard suggests absolutely the same words as in the browser.
In iOS Safari autocomplete="off" does not disable suggestions, one need to use autocorrect="off".
And just wanted to add a little that "autocorrect" attribute is not described in any RFC, but it's supported in Safari and worked some time ago in Chrome. Don't see anything bad to bring it back :)
,
Nov 8
,
Jan 10
Hello. Is it planned to be fixed in the upcoming Chrome versions? |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by chelamcherla@chromium.org
, Nov 6