ID:2146980
 
BYOND Version:511.1355
Operating System:Windows 7 Ultimate 64-bit
Web Browser:Chrome 52.0.2743.116
Applies to:Dream Seeker
Status: Open

Issue hasn't been assigned a status value.
I'm not sure if this is a bug or my two machines are just playing up on me.

Descriptive Problem Summary:
If you have an image that is a link in a browser the cursor icon will continuously flicker between the hand and the pointer. At first I believed this was an IE issue but the same html works fine in IE.

Numbered Steps to Reproduce Problem:
1. Have a browser control.
2. Output the code below.
3. Hover and move the mouse over the link and watch as the mouse flickers

Code Snippet (if applicable) to Reproduce Problem:
<html>
<body>
<a href=''><img src='' width=32px height=32px></a>
</body>
</html>

//The bug also occurs on variants of the above situation, such as having an image with onClick and changing the cursor with a style: <img src='' style="cursor:pointer" onClick="")


Expected Results:
The cursor to change to the hand icon.

Actual Results:
The cursor flickers between the hand icon and the pointer icon as you move it

Here is a small GIF of whats happening:

The entire grey box is a link, the mouse pointer should stay as the hand but it flickers to the pointer when you move it.

Does the problem occur:
Every time? Or how often? Every time
In other games? Unsure
In other user accounts? Yes
On other computers? Yes (tested on a Windows 10 machine and it returned the same results)

When does the problem NOT occur?
Never, it will always occur if an image is a link.

Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? (Visit http://www.byond.com/download/build to download old versions for testing.)
Also occurs in the stable release.

Workarounds:
None
Moved out of Beta Bugs because this is not specific to the beta. I'm also pretty sure this is an old bug and there's already a report for it.
Ah I wasn't sure whether or not to put it in beta bugs or the normal bugs, thanks for clearing that up.

I tried searching for other reports, only now did I find the report similar to this one, sorry!

If I find a workaround I'll be sure to update, thanks.