New issue
Advanced search Search tips

Issue 601344 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Apr 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Mouse cursor fails turning into pointer over links

Reported by arnaud.m...@ibrows.ch, Apr 7 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.110 Safari/537.36

Steps to reproduce the problem:
1. Hover over a link 

What is the expected behavior?
1. Mouse cursor should turn into a pointer (hand) 

What went wrong?
1. It does not turn into a pointer and stays as an arrow

Did this work before? N/A 

Chrome version: 49.0.2623.110  Channel: stable
OS Version: OS X 10.11.3
Flash Version: Shockwave Flash 21.0 r0

Very annoying for users and especially web developers!
 
Labels: Needs-Feedback
I can't reproduce this locally. Is there a specific page where this occurs? Does this happen in incognito mode?
I just updated to Version 49.0.2623.112 (64-bit) and the same happens.

It happens on all websites, incognito and normal browsing modes.

I just realized that this actually also happens with Safari and more or less with Firefox where the mouse cursor flickers but somehow ends up staying in pointer mode most of the time.

I guess you can close this issue as it doesn't seem to be related to Chrome only.
Just as a side note, an OS X update to 10.11.4 seems to have fixed all my issues.
Project Member

Comment 4 by sheriffbot@chromium.org, Apr 13 2016

Labels: -Needs-Feedback Needs-Review
Owner: ellyjo...@chromium.org
Thank you for providing more feedback. Adding requester "ellyjones@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://sites.google.com/a/chromium.org/dev/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Unconfirmed)
Curious. Possibly it was a misbehavior of the earlier OS X version, then. If it happens in Safari and Firefox as well, it seems likely that something was/is wrong at the system level instead of Chrome.

In any case, since the problem seems to be gone for you and I can't reproduce it here, I'm going to close the bug. Thanks for your report :)
Yes you can close it. Thank you!

Sign in to add a comment