commit | 078d9f4e633bf9d6fa6f8314a057d703d30fb519 | [log] [tgz] |
---|---|---|
author | Mikel Astiz <mastiz@chromium.org> | Wed Dec 15 11:59:14 2021 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Dec 15 11:59:14 2021 |
tree | 123f88f335ebbe1e06483a1580597bfd9b03b507 | |
parent | 7b06ca76362e9e3d497060981d9219376282fa4d [diff] |
Reland "[Passwords] Fix assertion failure when opening password settings" This is a reland of 293ef66ce69d271b8ff9288c6f0598688270ed0b, updated to avoid breaking PasswordSettingsTest#testManageAccountLinkSyncing() by making sure the test mimics sync having been fully initialized. Original change's description: > [Passwords] Fix assertion failure when opening password settings > > Method SyncService.isUsingExplicitPassphrase() has the precondition that > the sync engine must have initialized, as per isEngineInitialized(). To > avoiding running into assertion failures, PasswordManagerHelper must > first rule out ongoing initialization before invoking > isUsingExplicitPassphrase(). > > Change-Id: I8f519953c6d37aa4d9d54e6b043c24054fb46b45 > Fixed: 1276532 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3336879 > Reviewed-by: Ioana Pandele <ioanap@chromium.org> > Commit-Queue: Mikel Astiz <mastiz@chromium.org> > Cr-Commit-Position: refs/heads/main@{#951464} Change-Id: I280c58064ba674e1573c938002bdb301fc5d6533 Fixed: 1276532, 1279940 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3341531 Reviewed-by: Ioana Pandele <ioanap@chromium.org> Commit-Queue: Mikel Astiz <mastiz@chromium.org> Cr-Commit-Position: refs/heads/main@{#951898}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.