forked from chromium/chromium
-
-
Notifications
You must be signed in to change notification settings - Fork 17
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Reland "[ntp] Store collection ids for theme background images"
This is a reland of commit 20fca53 It adds default values for daily_refresh_enabled and collection_id to uploaded images since we now expect these for all CustomBackground structs. Also fixes the setting up of custom background in test (the main culprit). Original change's description: > [ntp] Store collection ids for theme background images > > This CL concerns the NTP handler. A follow up CL will bring the changes here to the Customize Chrome handler. > > Prior to this CL collection ids were only stored in user prefs ('prefs::kNtpCustomBackgroundDict') if daily refresh was turned on. > > Now, collection IDs will be stored anytime a theme is set. > > This CL obsoletes a test in ntp_custom_background_service_unittest.cc that makes sure collection ID takes priority over background URL. Before and after this CL, there are no calls to SetCustomBackground for daily refresh in the codebase where both URL and collection id are set (https://source.chromium.org/search?q=-file:out%20SetCustomBackgroundInfo%20-file:test). > > The changes in the CL will allow us to create a metric that stores the collection ID used by the user on NTP load. > > Change-Id: Ief491945ec77b6b06f56dc4ff42bad2774eb9ca4 > Bug: 1384258 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4183244 > Reviewed-by: Tibor Goldschwendt <tiborg@chromium.org> > Reviewed-by: Tom Sepez <tsepez@chromium.org> > Commit-Queue: Paul Adedeji <pauladedeji@google.com> > Reviewed-by: Riley Tatum <rtatum@google.com> > Cr-Commit-Position: refs/heads/main@{#1097166} (cherry picked from commit 5c7d381) Bug: 1384258 Change-Id: I101f478becf2eb412cca51c6fc919cf1eb7fc854 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4198399 Reviewed-by: Riley Tatum <rtatum@google.com> Reviewed-by: Tibor Goldschwendt <tiborg@chromium.org> Commit-Queue: Paul Adedeji <pauladedeji@google.com> Reviewed-by: Tom Sepez <tsepez@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1097786} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4205669 Reviewed-by: Mustafa Emre Acer <meacer@chromium.org> Commit-Queue: Riley Tatum <rtatum@google.com> Cr-Commit-Position: refs/branch-heads/5563@{#57} Cr-Branched-From: 3ac59a6-refs/heads/main@{#1097615}
- Loading branch information
Paul Adedeji
authored and
Chromium LUCI CQ
committed
Jan 31, 2023
1 parent
414cc26
commit af19370
Showing
12 changed files
with
89 additions
and
50 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.