New issue
Advanced search Search tips

Issue 663380 link

Starred by 3 users
Status: Duplicate
Merged: issue 663423
Owner:
se...@chromium.org
Closed: Nov 2016
Cc:
ma...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug



Sign in to add a comment

Date of birth field is misclassified as a credit card from

Project Member Reported by est...@chromium.org, Nov 8 2016 
Version: 56.0.2912.0
OS: Mac OS X

What steps will reproduce the problem?
(1) Visit http://sfelections.org/tools/vbmstatus/ with a stored credit card.
(2) Focus the MM Date of Birth field and press the down arrow key.

What is the expected output?
No message about credit cards, since the form isn't a credit card form.

What do you see instead?
Message about credit card autofill being disabled. (see screenshot)

Comment 1 by zkoch@chromium.org, Nov 8 2016

Cc: se...@chromium.org
This is another case of where the server is identifying a month as a CC expiration date. I thought we had changed the logic to require the presence of another CC field to trigger this?

Comment 2 by se...@chromium.org, Nov 8 2016 

Seems like the heuristics are working OK but the server predictions are wrong. Might be because people enter a MM that is the same as their credit card expiration. Will overwrite the server predictions for these for now. 

The long term solution would be to only fill when we see enough CC related fields (like the way the heuristics work).

Thanks for flagging this!

Comment 3 by est...@chromium.org, Nov 8 2016 

(forgot the screenshot, for posterity)

Thanks for the updates!
Screen Shot 2016-11-08 at 8.00.48 AM.png
102 KB View Download

Comment 4 by se...@chromium.org, Nov 8 2016

Cc: -se...@chromium.org ma...@chromium.org
Owner: se...@chromium.org

Comment 5 by se...@chromium.org, Nov 8 2016

Status: Fixed (was: Assigned)
The server overrides were commited. Closing this particular bug. Thanks!

Comment 6 by zkoch@chromium.org, Nov 8 2016 

Seb, do we have another bug that we're tracking for this generally? If so, I would merge this. Otherwise, we should keep this open as a general tracking bug.

Comment 7 by se...@chromium.org, Nov 8 2016

Mergedinto: 663423
Status: Duplicate (was: Fixed)
Right, let's merge into the bug for the general fix of this situation. Thanks.
►

Sign in to add a comment