commit | a4d579a429bfbdb819f55451fc022a1c4a87bd37 | [log] [tgz] |
---|---|---|
author | Andrey Davydov <andreydav@google.com> | Tue Jun 11 17:41:50 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jun 11 17:41:50 2024 |
tree | d87710772e22b76c04079da6c6e68aa03d165892 | |
parent | f137f5eb705b6f49aa7fbd1d0b21700e793c3b6e [diff] |
Add skeletons of FloatingSsoSyncBridge and FloatingSsoService FloatingSsoSyncBridge is the main part of Sync integration, FloatingSsoService is a KeyedService which will orchestrate the main feature logic. This cl adds their skeletons with lots of TODO comments referencing future work. Meaningful parts implemented here: - new feature flag to control the creation of FloatingSsoService - FloatingSsoService observes kFloatingSsoEnabled pref - two browser tests for points above - FloatingSsoServiceFactory overrides ServiceIsCreatedWithBrowserContext so that the service is created on profile creation - FloatingSsoServiceFactory specifies in its constructor that only regular profiles should have FloatingSsoService Design doc(internal): go/floating-sso-dd Bug: b:318391357, b:346354326, b:346354327 Change-Id: I683bef6867d6485fec6c1316c67bd3ed299099a7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5577196 Reviewed-by: Maria Petrisor <mpetrisor@chromium.org> Commit-Queue: Andrey Davydov <andreydav@google.com> Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com> Reviewed-by: Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/heads/main@{#1313539}
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.