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

Issue 818010 link

Starred by 5 users

Issue metadata

Status: Verified
Owner:
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug

Blocking:
issue 817957



Sign in to add a comment

Window resizer is broken on Chrome OS

Project Member Reported by x...@chromium.org, Mar 1 2018

Issue description

Chrome Version: 66.0.3359.0
OS: Chrome

What steps will reproduce the problem?
(1) Open a window in its normal state
(2) Use the mouse to select its edge to resize

What is the expected result?
The window can be resized normally

What happens instead?
The window is resized but the content in it is totally empty.

I'll attach a screenshot later.


 

Comment 1 by x...@chromium.org, Mar 1 2018

Note it only broke on device, on workstation (running Chrome for Chrome OS on Linux) it seems work fine. 

And actually it was more broken than I thought: not only the window resizer is broken, but most of the time the device doesn't respond the mouse/touch event.

Comment 2 by x...@chromium.org, Mar 2 2018

Just took a screenshot. See the attached screenshot.
Screenshot 2018-03-01 at 16.21.47.png
2.0 MB View Download

Comment 3 by x...@chromium.org, Mar 2 2018

Btw: It works fine in Chrome version 66.0.3357.0
Components: UI>Shell>WindowManager

Comment 5 by willg...@gmail.com, Mar 2 2018

I found that This issue and 818270 disappears when I disable the Play Store.

Comment 6 by x...@chromium.org, Mar 2 2018

Cc: skuhne@chromium.org edcourtney@chromium.org djacobo@chromium.org
Re#5: Thanks! It also seems the case for me. When Playstore is enabled, this issue and  Issue 818270  can both be observed.
+ A few Arc folks and Arc constable

Comment 7 by warx@chromium.org, Mar 2 2018

Cc: abodenha@chromium.org r...@chromium.org steve...@chromium.org
 Issue 818270  has been merged into this issue.
Hi, can test if reverting crrev.com/c/937820 fixes it?
Blocking: 817957
Owner: fdoray@chromium.org
Status: Assigned (was: Available)
Yep reverting fixed this. That CL was also causing  crbug.com/817957 .

Looks like fdoray@ is OOO until 3/12, so I'll revert this.

Comment 10 by x...@chromium.org, Mar 5 2018

Labels: Merge-Request-66
The culprit CL was landed in M66 while the revert CL was landed in M67.
Request merge for the revert CL https://chromium-review.googlesource.com/c/chromium/src/+/947802.
Cc: josa...@chromium.org
Labels: -Merge-Request-66 Merge-Approved-66

Comment 13 by x...@chromium.org, Mar 5 2018

Cc: aashuto...@chromium.org abod...@chromium.org avkodipelli@chromium.org songsuk@chromium.org dhadd...@chromium.org sdantul...@chromium.org
 Issue 818755  has been merged into this issue.

Comment 14 by x...@chromium.org, Mar 6 2018

Labels: -ReleaseBlock-Dev Merge-Merged
Oops. Sorry forgot to link the merge-to-M66 CL to this issue. 
The revert CL has been merged to M66, see https://chromium-review.googlesource.com/c/chromium/src/+/950140.

Remove RBD label. 

Labels: -Merge-Merged -Merge-Approved-66 ReleaseBlock-Dev Merge-Merged-66
re adding the RBD in case the fix is not working 

Also, can you mark as fixed if nothing else pending?

Comment 16 by x...@chromium.org, Mar 6 2018

Status: Fixed (was: Assigned)
Sure. 
Unable to repro this issue as per  Issue 818755  on build 66.0.3359.0/10452.0.0 dev-channel Reks which doesn't have the fix.Unable to repro the same on the latest available M-66, 66.0.3359.10/10452.1.0 dev-channel Reks so not sure whether this is indeed fixed.




Comment 18 by x...@chromium.org, Mar 6 2018

Re mmanchala: I think these issues only happened on Arc++ enabled devices. 
Status: Verified (was: Fixed)
Verified the fix on Chrome 66.0.3359.10/CrOS 10452.1.0 - Eve, Reks

Sign in to add a comment