New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 599713 link

Starred by 2 users
Status: WontFix
Owner:
x...@chromium.org
Closed: Aug 31
Cc:
█ bshe@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

A racing issue when syncing the surprise wallpaper

Project Member Reported by x...@chromium.org, Mar 31 2016 
OS: Chrome

Suppose there are two devices: A and B that have the same account. Device A enables 'Surprise Me' feature, then device B will receive two storage change events: Constants.AccessSyncSurpriseMeEnabledKey & Constants.AccessSyncWallpaperInfoKey. Constants.AccessSyncSurpriseMeEnabledKey change will fire a new surprise wallpaper on device B while Constants.AccessSyncWallpaperInfoKey change tries to sync down the surprise wallpaper from A. There is a chance that the wallpaper changes twice on device B.

Comment 1 by wzang@chromium.org, Aug 31

Status: WontFix (was: Assigned)
This case won't happen because |Constants.AccessLastSurpriseWallpaperChangedDate| will also sync to device B. According to the check at https://cs.chromium.org/chromium/src/chrome/browser/resources/chromeos/wallpaper_manager/js/event_page.js?l=139, device B will only update wallpaper once based on |Constants.AccessSyncWallpaperInfoKey|.
►

Sign in to add a comment