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

Issue 796857 link

Starred by 1 user
Status: WontFix
Owner:
wzang@chromium.org
Closed: Feb 2018
Cc:
ajha@chromium.org
zalcorn@chromium.org
abodenha@chromium.org
r...@chromium.org
alemate@chromium.org
█ brajkumar@chromium.org
jdufault@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression:Change of Wallpaper is seen while rotating display in Guest mode

Project Member Reported by rkalavakuntla@chromium.org, Dec 21 2017 
Chrome Version: 65.0.3299.0/10234.0.0 dev channel  Daisy,Kip & Reks
OS:Chrome OS

What steps will reproduce the problem?
(1)Recover Build >>In 'Sign into your chromebook' overlay >>Click 'Browse as Guest' and Observe the wallpaper of it
(2)Press Ctrl+Shift+Reload button to rotate display and Observe the change of wallpaper(Please refer video)

Actual:Change of Wallpaper is seen while clicking Ctrl+Shift+Reload button to rotate display
Expected: No such Change of Wallpaper should be seen while clicking Ctrl+Shift+Reload button to rotate display

This is a Regression issue as same is working fine in 65.0.3286.0/10191.0.0 dev channel daisy

Note:Issue is not seen in Linux,Windows OS
Actual.mp4
8.5 MB View Download
expected.mp4
10.5 MB View Download

Comment 1 by bhthompson@google.com, Feb 20 2018

Cc: abodenha@chromium.org
Whom is the right owner for this? 

This is marked as blocking stable 65 and we are only a few weeks away.

Comment 2 by abodenha@chromium.org, Feb 20 2018

Owner: r...@chromium.org
Is this still on wzang@'s plate?

Comment 3 by r...@chromium.org, Feb 20 2018

Cc: r...@chromium.org
Owner: wzang@chromium.org
Status: Assigned (was: Untriaged)
Yep.

Comment 4 by r...@chromium.org, Feb 20 2018

Cc: alemate@chromium.org jdufault@chromium.org zalcorn@chromium.org

Comment 5 by wzang@chromium.org, Feb 22 2018

Status: WontFix (was: Assigned)
Can't repro in 	65.0.3325.93 or in 66 builds. The issue was fixed by a subsequent refactoring CL.
►

Sign in to add a comment