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

Issue 789193 link

Starred by 1 user
Status: Fixed
Owner:
rogerm@chromium.org
Closed: Dec 2017
Cc:
se...@chromium.org
█ durgapandey@chromium.org
ma...@chromium.org
ios-bugs@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , iOS , Chrome , Mac
Pri: 3
Type: Bug



Sign in to add a comment

[autofill] Treat autocomplete=false the same as autocomplete=off

Project Member Reported by rogerm@chromium.org, Nov 28 2017 
Chrome autofill should treat autocomplete=false the same as autocomplete=off, which is to say: it should be subject to the same ignore/enable policy.
Project Member

Comment 1 by bugdroid1@chromium.org, Nov 28 2017 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/20c7806a04c50eb9646f1800e3642ba4fe8dd4f9

commit 20c7806a04c50eb9646f1800e3642ba4fe8dd4f9
Author: Roger McFarlane <rogerm@chromium.org>
Date: Tue Nov 28 19:18:38 2017

[autofill] Treat autocomplete=false the same as autocomplete=off

This CL makes Chrome treat a field with autocomplete=false the same
as one with autocomplete=off, instread of treating autocomplete=false
as an unrecognized/unsupported type identifier.

Bug:  789193 
Change-Id: I80b4690e904b549775a0f055fa7f5df13d519e14
Reviewed-on: https://chromium-review.googlesource.com/794034
Commit-Queue: Roger McFarlane <rogerm@chromium.org>
Commit-Queue: Sebastien Seguin-Gagnon <sebsg@chromium.org>
Reviewed-by: Sebastien Seguin-Gagnon <sebsg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519783}
[modify] https://crrev.com/20c7806a04c50eb9646f1800e3642ba4fe8dd4f9/components/autofill/core/browser/form_structure.cc
[modify] https://crrev.com/20c7806a04c50eb9646f1800e3642ba4fe8dd4f9/components/autofill/core/browser/form_structure_unittest.cc

Comment 2 by rogerm@chromium.org, Dec 4 2017

Status: Fixed (was: Started)
►

Sign in to add a comment