commit | 2c3867d8d02fa19ecb75548e1610b05ef23291a8 | [log] [tgz] |
---|---|---|
author | David Black <dmblack@google.com> | Thu May 19 05:29:22 2022 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu May 19 05:29:22 2022 |
tree | d8c8d04e5edcdec0a9741fac46eb08aa93f68b89 | |
parent | 30de8e19178e74e1db8214c046e1055d889d8dbd [diff] |
personalization: Handle dedup key for Google Photos wallpapers. Problem: Google Photos photos are uniquely identified by id but the same photo in multiple albums will have a unique id per album. This makes it impossible for us to determine whether a given photo from one album refers to the same photo in another. Solution: Google Photos photos are mapped to a dedup key that is the same for a given photo across multiple albums. This makes it possible to determine whether a given photo from one album refers to the same photo in another. Note: Backwards compatibility is important to consider due to cross device sync. In this CL, a new attribute is synced for dedup key. Old clients will not deserialize the new attribute and will therefore continue to fall back to matching by id. If an old client sets a Google Photos wallpaper, the new client will not deserialize a dedup key and so will fall back to matching by id. Before: http://shortn/_Q04RVVnAcK After: http://shortn/_cR7BpNWHEy Bug: b:232990402 Change-Id: I19db4415bd4b12f2bede5662a2e6f624264998fd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3653296 Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org> Reviewed-by: Sam McNally <sammc@chromium.org> Commit-Queue: David Black <dmblack@google.com> Cr-Commit-Position: refs/heads/main@{#1005120}
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.