Autofil: behavior on <input type=number> fields
Reported by
teo8...@gmail.com,
Dec 10 2016
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.75 Safari/537.36 Steps to reproduce the problem: Unfortunately I cannot provide an URL that reproduces the issue. I have tried to build a minimal example here: http://output.jsbin.com/bijurejeda but it does NOT reproduce the issue 1. I visit a page that contains a form (it's a forum admin control panel page with some settings) which has several number input fields (i.e. input fields with type="number"). Some of the field happen to have descriptions that contain the word "teléfono" ("telephone" in spanish), one other happens to have a description that contains the word "dirección" ("address" in spanish). However, the form has nothing to do with a form for personal data, and it doesn't even remotely look like it. The number input fields are all pre-field with a value 2. click on one of the input fields whose description contains the word "teléfono" 3. delete the current value 4. start typing any number What is the expected behavior? What went wrong? I guess Chromoe's brilliant "intelligent" autofill system thinks that this is a form for filling in personal data such as a telephone number and address, just because the words "telephone" and "address" happen to appear within the (pretty long) texts next to the input fields (by the way, these are not even html label tags, nor do the input field names look like anything related to telephones or addresses). So, it triggers the autofill behavior, which is already idiotic in the first place. But the worst part is that, after I start typing a number into the input field, if I happen to move the mouse cursor over the suggestions (even accidentally and without clicking on any of them), THE NUMBERS I HAVE TYPED ARE DELETED leaving the field empty. Did this work before? N/A Chrome version: 55.0.2883.75 Channel: stable OS Version: Flash Version: Shockwave Flash 23.0 r0
,
Dec 12 2016
,
Dec 12 2016
Hi Teo, I can't repro the Autofill behavior on your example link from jsbin using the same Chrome version. However, forcing its hand a little bit with "autocomplete" attributes I can get Autofill to trigger, which doesn't seem right for this kind of input field (number) where numbers are probably expected to be low. We will look at addressing that.
,
Dec 12 2016
,
Dec 12 2016
> I can't repro the Autofill behavior on your example link from jsbin Yeah I can't either. It's just as close a minimal example as I could think of that seemed to resemble my real use case which unfortunately I cannot share. I hoped it would be better than nothing.
,
May 1 2018
,
Aug 3
This bug has an owner, thus, it's been triaged. Changing status to "assigned". |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by ajha@chromium.org
, Dec 12 2016Labels: M-55