32

I currently have a C# host that mirrors the screen and mouse on a website, the connection works totally fine, and when the mouse changes on the host, it changes the CSS almost immediatly. This way I can mirror the mouse too.

So here is the problem:

The mouse only updates when I move the mouse on the client website.

Speed and performance is very important here, a quick fix would be to refresh the canvas, or move the page/mouse a little bit, but I'd rather have a more sophisticated approach.

Alexander
  • 1,554
  • 2
  • 16
  • 23
  • There is a chrome bug thread here: https://bugs.chromium.org/p/chromium/issues/detail?id=26723 – Ben Boyle Oct 22 '16 at 06:07
  • 1
    Generally you can set a class to the body with a cursor style, and then remove that class to force an update. – Mark Nov 02 '16 at 19:47
  • 1
    Possible duplicate of [Getting the browser cursor from "wait" to "auto" without the user moving the mouse](http://stackoverflow.com/questions/1718415/getting-the-browser-cursor-from-wait-to-auto-without-the-user-moving-the-mou) – rjmunro Jan 27 '17 at 23:49
  • 1
    @Alexander please mark my answer if it solved your question =) thanks! – Facundo Colombier Nov 29 '17 at 23:47
  • 1
    @FacundoColombier Ah I forgot :D – Alexander Nov 30 '17 at 19:09

1 Answers1

66

you should check one of the answers given in the link that @rjmunro linked, it says:

I believe this issue (including the mousedown problem) is now fixed in Chrome 50.

But only if you are not using the developer tools!!

Close the tools and the cursor should immediately respond better.

Getting the browser cursor from "wait" to "auto" without the user moving the mouse

Facundo Colombier
  • 3,487
  • 1
  • 34
  • 40
  • 13
    Thank goodness for this answer, i might have spent hours debugging. Thank you! – Partack May 18 '17 at 05:06
  • 9
    Sounds like a prank some Chrome employee thought of, "Let's make it so that the bug is fixed right when the debugger stops looking for it!" – Radvylf Programs Apr 14 '18 at 23:53
  • Wow! A rare case where laziness and/or procrastination is actually the solution! – philippe_b Aug 06 '18 at 16:53
  • 3
    Did this bug reappear on Chrome? It requires moving the mouse once again, even with dev tools closed – QuantumBlack May 13 '19 at 08:10
  • 1
    @Shocker I'm not sure it's related to devtools. Sometimes it works with devtools open and sometimes it doesn't work with devtools closed. Refresh doesn't fix it, but closing the tab and reopening it does. – Rivenfall May 21 '19 at 14:50
  • 1
    Please blod "Close the tools and the cursor should immediately respond better." :D – Noman_1 Feb 01 '21 at 12:25
  • 3
    can confirm this still happens today with dev tools open. what a waste of time! – mukunda Jun 27 '21 at 02:02
  • 1
    with chorme 87 and electron 11.4 this is still an issue, and closing the dev tools still show the error – Coding Edgar Dec 19 '21 at 17:47