New issue
Advanced search Search tips

Issue 617827 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

radio button autofill missing

Reported by jidanni@gmail.com, Jun 7 2016

Issue description

UserAgent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.79 Safari/537.36

Steps to reproduce the problem:
Form auto fill knows about names, addresses, but when confronted with ()Male ()Female, one has to type it in by hand each time.

What is the expected behavior?

What went wrong?
Built in autofill only knows about text fields, not radio buttons.

One must install extensions to push the radio buttons.

Did this work before? N/A 

Chrome version: 51.0.2704.79  Channel: n/a
OS Version: 
Flash Version: 

Seen on https://cwbebox.cwb.gov.tw/ebox_formfill/ebox_visFormFill.php
 

Comment 1 by tkent@chromium.org, Jun 7 2016

Components: -UI UI>Browser>Autofill
Labels: M-53 OS-Mac OS-Windows
Status: Untriaged (was: Unconfirmed)
Considering the above issue as a Feature-Request and marking it as untriaged.


Comment 3 by zkoch@chromium.org, Jun 8 2016

Labels: -M-53
I'm not sure there are too many use cases where radio button support in autofill makes sense. Right now we limit the data we autofill to (chrome://settings/Autofill), none of which are super appropriate for a radio button. In your example of Male and Female, this isn't information that Chrome stores. Do you have an example from the real world where you think Autofill for radio buttons would be useful?

Comment 4 by jidanni@gmail.com, Jun 9 2016

My real world example is right there in Comment 0.

Comment 5 by jidanni@gmail.com, Oct 8 2017

You mean
chrome://settings/autofill
not
chrome://settings/Autofill !

Comment 6 by jidanni@gmail.com, Oct 8 2017

Curretly with
Version 61.0.3163.100 (Developer Build) built on Debian buster/sid, running on Debian buster/sid (64-bit)
the problem remains.
The user frustratingly has to click his gender each time over again when submitting the form, as it is a required item.
If you think about it, gender rarely changes... it is the most unchanging item of any personal information. Only birthday will change even less. So chrome should remember it.

That is from the user's perspective.
(From chromium's perspective, I wouldn't want to have to parse for the text "gender".)

Sign in to add a comment