Issue metadata
Sign in to add a comment
|
Regression: [DevTools]Mouse pointer doesn’t change it state on hovering.
Reported by
dchau...@etouch.net,
Jun 13 2018
|
||||||||||||||||||||||
Issue descriptionChrome Version: 68.0.3440.25 (Official Build) (64-bit) Revision 2ae8d1b3e748e1d64948045b2e1fb269a4098373-refs/branch-heads/3440@{#328} OS: Mac OS X(10.12.6,10.13.1, 10.13.5, 10.13.6). What steps will reproduce the problem? 1. Launch Chrome, go to NTP, open DevTools and dock it to bottom. 2. Hover the mouse pointer on the header of DevTools (bidirectional arrow will appear). 3. Now move the mouse pointer on NTP and observe the mouse pointer. Actual: Bidirectional arrow pointer doesn’t get changed to arrow pointer. Expected: Bidirectional arrow pointer should get changed to arrow pointer. This is a regression issue, broken in M-68 series, below is manual regression range: Good build: 68.0.3401.0 (Revision: 552222) Bad build: 68.0.3402.0 (Revision: 552545) Using the per-revision bisect providing the bisect results: You are probably looking for a change made after 552275 (known good), but no later than 552276 (first known bad). CHANGELOG URL: The script might not always return single CL as suspect as some perf builds might get missing due to failure. https://chromium.googlesource.com/chromium/src/+log/f582ff2a8dd2e14e5f9140bfd5b3bfc1b68a9e7a..3fef335bdba3410b39b2d50a843e372e42bf01b7 Suspecting: https://chromium.googlesource.com/chromium/src/+/3fef335bdba3410b39b2d50a843e372e42bf01b7 @wjmaclean: Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner. Note: 1. This issue is not reproducible on Windows (7,8,8.1,10) & Linux (14.04 LTS) OS. 2. This issue is also reproducible on Canary #69.0.3457.0 3. To reproduce the issue frequently kindly perform the above steps multiple times. (Refer attached Video) Kindly review the attached screen-cast for reference. Thank you.
,
Aug 16
With response to comment #1: Retested this issue on Mac OS X(10.12.6, 10.13.1, 10.14, 10.13.6) machines using latest Canary #70.0.3524.0 and it seems to be fixed and working as intended. Attaching screen-cast for the same. Thank you.
,
Aug 16
Thanks for checking dchaubey@ ... let's mark this as fixed, and it can be re-opened if needed. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by wjmaclean@chromium.org
, Aug 14