New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 657353 link

Starred by 5 users

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Autofill only populates last name of double barrelled surnames

Reported by ed.go...@gmail.com, Oct 19 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36

Steps to reproduce the problem:
1. Add "Edward Hartwell Goose" as the name in the auto fill settings
2. Visit a form which asks for name. I'm looking at the sign up one for StubHub (https://www.stubhub.co.uk/sell/hub/login) at the moment, but it's pretty universal.
3. Confirm that the Surname field is incorrectly populated with only "Goose"

What is the expected behavior?
My full name is "Edward Hartwell Goose" - of which Edward is my first name,  and "Hartwell Goose" is my surname. My surname contains no punctuation (e.g. a hyphen). I therefore expect the Surname field to be populated with "Hartwell Goose".

Adding my middle name (i.e. Edward Xyz Hartwell Goose) to Autofill exacerbates the problem. In this case the name field becomes "Edward Xyz" and the surname remains "Goose"

What went wrong?
Autofill incorrectly assumes that Hartwell in Edward Hartwell Goose is my middle name and omits it from auto fill. I have to correct it every single time and it drives me nuts.

Did this work before? N/A 

Chrome version: 53.0.2785.143  Channel: stable
OS Version: OS X 10.11.5
Flash Version: Shockwave Flash 23.0 r0

I appreciate this is the nichest of niche issues. But it does wind me up, and splitting the name field in autofill into Firstname Surname would be more accurate for me, and others who share my affliction of more than 1 word in my surname.
 
Components: -UI UI>Browser>Autofill
Owner: zkoch@chromium.org
Status: Untriaged (was: Unconfirmed)
zkoch@, can you take a look at this? I have not tested locally.

Comment 2 by zkoch@chromium.org, Oct 24 2016

Cc: ma...@chromium.org se...@chromium.org
Yeah, this is something we struggle with.

Ed, did you add your information manually in chrome://autofill/settings? Or was it auto-created by Chrome?
Status: Assigned (was: Untriaged)

Comment 4 by ed.go...@gmail.com, Nov 5 2016

I'm afraid I'm not sure - I don't remember setting it up but that might just be a failure of memory.

If it helps - this seems to be a problem consistently across devices and I tend to sign into devices and sync everything rather than manually setting them up. So I guess it's the latter?
Is it not possible to just have separate fields for first, middle and last names? This is very annoying for me, because I have a double last name as well.
I have the same problem. My first name is 3 words and using auto-fill to insert my first name in a form, only one word from the 3 words is inserted.

As it is very common that forms on the web request for First and Family name separately, it is rational to keep them separate in auto-fill entries.

Comment 7 by thomasvs@google.com, Oct 17 2017

This annoys me terribly too.

This is a clear example of a bug that makes the product less inclusive and hurts diversity.  I appreciate that American society has trouble with surnames that are more than one word, or multiple surnames, and an inexplicable focus on initials or middle names, but it is very common outside of the US.  It's all the more surprising given that the US is a country of immigrants.

The root problem seems to be that Chrome takes in a "name" and tries to guess what parts are first and last name, and fails to do so except for the most simple case.  There is no way in the UI to correct for it either.

Comment 8 by thomasvs@google.com, Oct 17 2017

I suggest changing the subject of the bug to be clearer:
"autofill only fills in the last word of a multi-word surname"
Related to Issue 779638
Status: Untriaged (was: Assigned)
Status: Assigned (was: Untriaged)
This bug has an owner, thus, it's been triaged. Changing status to "assigned".

Sign in to add a comment