New issue
Advanced search Search tips

Issue 882941 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Nov 20
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Using ShouldBeUploaded is inconsistent across Autofill and Password Manager.

Project Member Reported by dvadym@chromium.org, Sep 11

Issue description

For checking whether to upload votes for a form, function FormStructure::ShouldBeUploaded used both from Autofill and Password Manager code. Because Password Manager uploads votes rarely it's ok to upload Password Manager votes for any form, so call of this function might be skipped in Password Manager code.

On other hand, ShouldBeUploaded has check on |has_password_field_| and as result uploads for any password form are treated as Password Manager uploads, while they may come from Autofill.

So the solution:

1.Remove call of ShouldBeUploaded in Password Manager code.
2.Remove checks on has_password_field_ in ShouldBeUploaded.
 
Project Member

Comment 1 by bugdroid1@chromium.org, Sep 26

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

commit 1567a35a494568bcb8ee68d855e7f6176c182878
Author: Vadym Doroshenko <dvadym@chromium.org>
Date: Wed Sep 26 16:16:33 2018

Make function ShouldBeUploaded more consistent.

For checking whether to upload votes for a form, FormStructure::ShouldBeUploaded is called
both from Autofill and Password Manager code. Because Password Manager uploads votes rarely it's
ok to upload Password Manager votes for any form, so call of this function might be skipped in
Password Manager code.

On other hand, ShouldBeUploaded has a check on |has_password_field_| and as result uploads for
any password form are treated as Password Manager uploads, while they may come from Autofill.

This CL implements:
1.Removing call of ShouldBeUploaded in Password Manager code.
2.Removing checks on has_password_field_ in ShouldBeUploaded.

Bug:882941

Change-Id: Iba9ab1f74451520f0a636e0748f795d73e922ce7
Reviewed-on: https://chromium-review.googlesource.com/1219710
Commit-Queue: Vadym Doroshenko <dvadym@chromium.org>
Reviewed-by: Roger McFarlane <rogerm@chromium.org>
Reviewed-by: Dominic Battré <battre@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594335}
[modify] https://crrev.com/1567a35a494568bcb8ee68d855e7f6176c182878/components/autofill/core/browser/autofill_manager_unittest.cc
[modify] https://crrev.com/1567a35a494568bcb8ee68d855e7f6176c182878/components/autofill/core/browser/form_structure.cc
[modify] https://crrev.com/1567a35a494568bcb8ee68d855e7f6176c182878/components/autofill/core/browser/form_structure.h
[modify] https://crrev.com/1567a35a494568bcb8ee68d855e7f6176c182878/components/autofill/core/browser/form_structure_unittest.cc
[modify] https://crrev.com/1567a35a494568bcb8ee68d855e7f6176c182878/components/password_manager/core/browser/password_form_manager_unittest.cc
[modify] https://crrev.com/1567a35a494568bcb8ee68d855e7f6176c182878/components/password_manager/core/browser/votes_uploader.cc
[modify] https://crrev.com/1567a35a494568bcb8ee68d855e7f6176c182878/components/password_manager/core/browser/votes_uploader.h

Labels: Merge-Request-70
This is a small and non-risky CL. 

It is required in order to support password generation (which is launched in M-69) on sign-up forms with 2 fields and to improve Password Manager filling.
Project Member

Comment 3 by sheriffbot@chromium.org, Oct 1

Labels: -Merge-Request-70 Merge-Review-70 Hotlist-Merge-Review
This bug requires manual review: M70 has already been promoted to the beta branch, so this requires manual review
Please contact the milestone owner if you have questions.
Owners: benmason@(Android), kariahda@(iOS), geohsu@(ChromeOS), abdulsyed@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Let's target this for M71. Seems like this isn't absolutely critical and that M69 currently has this issue?
Hi Abdul,

generally, you're right of course. But in this specific case, this small CL is a complete blocker for some of our most important annual goals. I'm happy to provide more context offline. But it would be really good to get approval on this merge.

Thanks

Patrick
How safe is this merge overall?
Labels: -Merge-Review-70 Merge-Approved-70
Approving merge for M70. branch:3538. 

Already confirmed in #2 that this is safe cl. 
Project Member

Comment 8 by bugdroid1@chromium.org, Oct 2

Labels: -merge-approved-70 merge-merged-3538
The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/194e89dde24c20c5fe48f0b0b4a140a127d4ae76

commit 194e89dde24c20c5fe48f0b0b4a140a127d4ae76
Author: Vadym Doroshenko <dvadym@chromium.org>
Date: Tue Oct 02 18:34:03 2018

[MERGE] Make function ShouldBeUploaded more consistent.

For checking whether to upload votes for a form, FormStructure::ShouldBeUploaded is called
both from Autofill and Password Manager code. Because Password Manager uploads votes rarely it's
ok to upload Password Manager votes for any form, so call of this function might be skipped in
Password Manager code.

On other hand, ShouldBeUploaded has a check on |has_password_field_| and as result uploads for
any password form are treated as Password Manager uploads, while they may come from Autofill.

This CL implements:
1.Removing call of ShouldBeUploaded in Password Manager code.
2.Removing checks on has_password_field_ in ShouldBeUploaded.

Bug:882941

Change-Id: Iba9ab1f74451520f0a636e0748f795d73e922ce7
Reviewed-on: https://chromium-review.googlesource.com/1219710
Commit-Queue: Vadym Doroshenko <dvadym@chromium.org>
Reviewed-by: Roger McFarlane <rogerm@chromium.org>
Reviewed-by: Dominic Battré <battre@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#594335}(cherry picked from commit 1567a35a494568bcb8ee68d855e7f6176c182878)
Reviewed-on: https://chromium-review.googlesource.com/c/1257551
Cr-Commit-Position: refs/branch-heads/3538@{#826}
Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811}
[modify] https://crrev.com/194e89dde24c20c5fe48f0b0b4a140a127d4ae76/components/autofill/core/browser/autofill_manager_unittest.cc
[modify] https://crrev.com/194e89dde24c20c5fe48f0b0b4a140a127d4ae76/components/autofill/core/browser/form_structure.cc
[modify] https://crrev.com/194e89dde24c20c5fe48f0b0b4a140a127d4ae76/components/autofill/core/browser/form_structure.h
[modify] https://crrev.com/194e89dde24c20c5fe48f0b0b4a140a127d4ae76/components/autofill/core/browser/form_structure_unittest.cc
[modify] https://crrev.com/194e89dde24c20c5fe48f0b0b4a140a127d4ae76/components/password_manager/core/browser/password_form_manager_unittest.cc
[modify] https://crrev.com/194e89dde24c20c5fe48f0b0b4a140a127d4ae76/components/password_manager/core/browser/votes_uploader.cc
[modify] https://crrev.com/194e89dde24c20c5fe48f0b0b4a140a127d4ae76/components/password_manager/core/browser/votes_uploader.h

Labels: Merge-Merged-70-3538
The following revision refers to this bug: 
https://chromium.googlesource.com/chromium/src.git/+/194e89dde24c20c5fe48f0b0b4a140a127d4ae76

Commit: 194e89dde24c20c5fe48f0b0b4a140a127d4ae76
Author: dvadym@chromium.org
Commiter: rogerm@chromium.org
Date: 2018-10-02 18:34:03 +0000 UTC

[MERGE] Make function ShouldBeUploaded more consistent.

For checking whether to upload votes for a form, FormStructure::ShouldBeUploaded is called
both from Autofill and Password Manager code. Because Password Manager uploads votes rarely it's
ok to upload Password Manager votes for any form, so call of this function might be skipped in
Password Manager code.

On other hand, ShouldBeUploaded has a check on |has_password_field_| and as result uploads for
any password form are treated as Password Manager uploads, while they may come from Autofill.

This CL implements:
1.Removing call of ShouldBeUploaded in Password Manager code.
2.Removing checks on has_password_field_ in ShouldBeUploaded.

Bug:882941

Change-Id: Iba9ab1f74451520f0a636e0748f795d73e922ce7
Reviewed-on: https://chromium-review.googlesource.com/1219710
Commit-Queue: Vadym Doroshenko <dvadym@chromium.org>
Reviewed-by: Roger McFarlane <rogerm@chromium.org>
Reviewed-by: Dominic Battré <battre@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#594335}(cherry picked from commit 1567a35a494568bcb8ee68d855e7f6176c182878)
Reviewed-on: https://chromium-review.googlesource.com/c/1257551
Cr-Commit-Position: refs/branch-heads/3538@{#826}
Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811}
Status: Fixed (was: Started)

Sign in to add a comment