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

Issue 616279 link

Starred by 1 user
Status: Fixed
Owner:
█ e...@chromium.org
Last visit > 30 days ago
Closed: Jun 2016
Cc:
mustash-bugs@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Regression in cursors on mash

Project Member Reported by e...@chromium.org, May 31 2016 
Running chrome --mash, the cursors no longer change when moving the mouse over the window borders.

Patch 65f37925f / https://codereview.chromium.org/1995983002 somehow broke changing cursors under mus+ash. I bisected to that CL; cursors still worked on the previous commit, a46cbfa5f. I don't know why this happened.

This wasn't caught by the CursorTests in mus_ws_unittests.

Comment 1 by pkasting@chromium.org, May 31 2016 

Strange.  The mash/ changes there certainly seem like they can't have any effect.

Comment 2 by e...@chromium.org, May 31 2016

Cc: -pkasting@chromium.org
Summary: Regression in cursors on mash (was: Regression in cursors on mash as a side effect of DISALLOW_COPY_AND_ASSIGN patch)
This might not be the patch. After a local revert didn't fix the problem, I did a clobber build at 65f37925f and retested and the cursors still worked.

Yay nondeterministic build behaviour. I guess I'm now doing a clobber bisect. :(

Comment 3 by e...@chromium.org, Jun 2 2016

Status: Fixed (was: Assigned)
Fixed with https://codereview.chromium.org/2027283002/

Comment 4 by lafo...@chromium.org, Feb 26 2018

Components: -MUS Internals>Services>WindowService
►

Sign in to add a comment