|
|
Chromium Code Reviews|
Created:
4 years, 6 months ago by melandory Modified:
4 years, 6 months ago Reviewers:
vabr (Chromium) CC:
chromium-reviews, gcasto+watchlist_chromium.org, vabr+watchlistpasswordmanager_chromium.org, mkwst+watchlist-passwords_chromium.org Base URL:
https://chromium.googlesource.com/chromium/src.git@master Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionDon't sync pref which controls the password manager to mobile.
Chrome will start sync prefs on mobile. It's not desired behaviour for the password manager pref, because it collides with the prefs reconciliation.
BUG=622620
Committed: https://crrev.com/9352a69e3b8cbf81e7a46dd9ea07a7e05ece94ee
Cr-Commit-Position: refs/heads/master@{#401592}
Patch Set 1 #Patch Set 2 : Don't sync pref which controls the password manager to mobile. #
Total comments: 2
Patch Set 3 : Proper init. #Messages
Total messages: 21 (11 generated)
Patchset #2 (id:20001) has been deleted
melandory@chromium.org changed reviewers: + vabr@chromium.org
Vaclav, PTAL, thanks!
Hi Tanja, while the code looks good (as in: it implements what your CL description says), could you also provide the context for this change? There should definitely be a bug associated to this CL, explaining why the preference is now not synced on mobile. Thanks, Vaclav
Description was changed from ========== Don't sync pref which controls the password manager to mobile. BUG=NONE ========== to ========== Don't sync pref which controls the password manager to mobile. Chrome will start sync prefs on mobile. It's not desired behaviour for the password manager pref, because it collides with the prefs reconciliation. BUG=NONE ==========
Description was changed from ========== Don't sync pref which controls the password manager to mobile. Chrome will start sync prefs on mobile. It's not desired behaviour for the password manager pref, because it collides with the prefs reconciliation. BUG=NONE ========== to ========== Don't sync pref which controls the password manager to mobile. Chrome will start sync prefs on mobile. It's not desired behaviour for the password manager pref, because it collides with the prefs reconciliation. BUG=622620 ==========
On 2016/06/22 05:52:51, vabr (Chromium) wrote: > Hi Tanja, while the code looks good (as in: it implements what your CL > description says), could you also provide the context for this change? There > should definitely be a bug associated to this CL, explaining why the preference > is now not synced on mobile. > > Thanks, > Vaclav PTAL.
LGTM, thank you! Cheers, Vaclav https://codereview.chromium.org/2084033002/diff/40001/components/password_man... File components/password_manager/core/browser/password_manager.cc (right): https://codereview.chromium.org/2084033002/diff/40001/components/password_man... components/password_manager/core/browser/password_manager.cc:140: flags = PrefRegistry::NO_REGISTRATION_FLAGS; Could you make the assignments on lines 140 and 142 definitions and remove line 138? As in: #if defined(OS_IOS) || defined(OS_ANDROID) uint32_t flags = PrefRegistry::NO_REGISTRATION_FLAGS; #else uint32_t flags = user_prefs::PrefRegistrySyncable::SYNCABLE_PREF; #endif It is a bit of a hazard to leave variables uninitialised, even though the current code proceeds with the initialisation immediately after definition.
Patchset #3 (id:60001) has been deleted
https://codereview.chromium.org/2084033002/diff/40001/components/password_man... File components/password_manager/core/browser/password_manager.cc (right): https://codereview.chromium.org/2084033002/diff/40001/components/password_man... components/password_manager/core/browser/password_manager.cc:140: flags = PrefRegistry::NO_REGISTRATION_FLAGS; On 2016/06/23 10:51:10, vabr (Chromium) wrote: > Could you make the assignments on lines 140 and 142 definitions and remove line > 138? As in: > #if defined(OS_IOS) || defined(OS_ANDROID) > uint32_t flags = PrefRegistry::NO_REGISTRATION_FLAGS; > #else > uint32_t flags = user_prefs::PrefRegistrySyncable::SYNCABLE_PREF; > #endif > > It is a bit of a hazard to leave variables uninitialised, even though the > current code proceeds with the initialisation immediately after definition. Done.
The CQ bit was checked by melandory@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/2084033002/80001
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
The CQ bit was checked by melandory@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from vabr@chromium.org Link to the patchset: https://codereview.chromium.org/2084033002/#ps80001 (title: "Proper init.")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/2084033002/80001
Message was sent while issue was closed.
Description was changed from ========== Don't sync pref which controls the password manager to mobile. Chrome will start sync prefs on mobile. It's not desired behaviour for the password manager pref, because it collides with the prefs reconciliation. BUG=622620 ========== to ========== Don't sync pref which controls the password manager to mobile. Chrome will start sync prefs on mobile. It's not desired behaviour for the password manager pref, because it collides with the prefs reconciliation. BUG=622620 ==========
Message was sent while issue was closed.
Committed patchset #3 (id:80001)
Message was sent while issue was closed.
Description was changed from ========== Don't sync pref which controls the password manager to mobile. Chrome will start sync prefs on mobile. It's not desired behaviour for the password manager pref, because it collides with the prefs reconciliation. BUG=622620 ========== to ========== Don't sync pref which controls the password manager to mobile. Chrome will start sync prefs on mobile. It's not desired behaviour for the password manager pref, because it collides with the prefs reconciliation. BUG=622620 Committed: https://crrev.com/9352a69e3b8cbf81e7a46dd9ea07a7e05ece94ee Cr-Commit-Position: refs/heads/master@{#401592} ==========
Message was sent while issue was closed.
Patchset 3 (id:??) landed as https://crrev.com/9352a69e3b8cbf81e7a46dd9ea07a7e05ece94ee Cr-Commit-Position: refs/heads/master@{#401592} |
