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

Issue 628227 link

Starred by 2 users

Issue metadata

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



Sign in to add a comment

Full name field not detected for Korean in Autofill

Project Member Reported by nicolaso@google.com, Jul 14 2016

Issue description

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

Steps to reproduce the problem:
Go to any of the following websites. Autofill does not offer completions for the "Full Name" ("이름") field.

1. Naver Signup (check all the boxes, and click "동의"): https://nid.naver.com/user2/join.nhn?m=init&lang=ko_KR
2. Chosun Media Signup: https://membership.chosun.com/joinN/regist/abroadmember/abMemJoin_2014.jsp
3. Twitter Signup (has autocomplete="off", but fields still aren't detected): https://twitter.com/signup?lang=ko

What is the expected behavior?
Autofill offers full name completions for the "이름" field. Note that "이름" can mean either "full name", or "given name", depending on the context.

What went wrong?
Autofill does not offer completions. This seems to be because of the regular expressions we use for the full name field. It seems we only use "성명" to detect a full name field; we might also want to accept "이름", but make sure that "이름" still works when it means "first name".

https://cs.chromium.org/chromium/src/components/autofill/core/browser/autofill_regex_constants.cc?l=239

Did this work before? N/A 

Chrome version: 51.0.2704.106  Channel: stable
OS Version: 
Flash Version: Shockwave Flash 22.0 r0
 
Project Member

Comment 1 by sheriffbot@chromium.org, Jul 15 2016

Labels: Hotlist-Google
Cc: rnimmagadda@chromium.org
Components: UI>Browser>Autofill
Labels: M-52 OS-Mac OS-Windows
Status: Untriaged (was: Unconfirmed)
Able to repro this issue on Windows 7, MAC (10.11.5) & Ubuntu Trusty (14.04) for Google Chrome Stable Version - 51.0.2704.106

This is a Non-Regression issue existing from M30 - # 30.0.1549.0

Sign in to add a comment