Issue metadata
Sign in to add a comment
|
Cursor is not immediately updated when pressing keys
Reported by
dennis.f...@gmail.com,
Nov 24 2016
|
||||||||||||||||||||
Issue description
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.98 Safari/537.36
Steps to reproduce the problem:
1. Subscribe to keydown even on body
2. Change cursor to crosshair in the event handler
3. Press any letter on the keyboard and do not move the mouse
Here is an example:
<html style="height: 100%; width: 100%">
<body style="height: 100%; width: 100%">
1. Try pressing any letter on the keyboard and do NOT move the mouse. <br/>
Cursor should change to crosshair, but it does not until the mouse is moved.
<br/>
2. Now refresh the page and try pressing any key modifier - Shift, Ctrl, Alt, etc. <br/>
Cursor does change immediately.
<br/>
<script>
document.addEventListener("keydown", function(){
document.body.style.cursor = "crosshair";
console.log("changed cursor");
});
</script>
</body>
</html>
What is the expected behavior?
The cursor should immediately change, just like when you press Ctrl, Alt, or Shift. Why should there be any difference?
What went wrong?
The browser is waiting for the mouse to be moved.
Did this work before? No
Chrome version: 54.0.2840.98 Channel: stable
OS Version: OS X 10.10.5
Flash Version: Shockwave Flash 23.0 r0
I don't think this ever worked before and it seems it does not work in other browsers either (tested Firefox, IE).
But I think this tiny thing is a MUST for modern rich applications which are changing cursor in reaction to hotkeys...
It would be amazing if it worked in Chrome, showing others the way to go ;)
,
Nov 29 2016
Test page: http://output.jsbin.com/buloyep I would expect this to work (based on the cursor update timer which watches for cursor style changes). Works correctly for me on: Chrome 56.0.2924.3 Linux Chrome 54.0.2840.99 Windows Chrome 54.0.2840.98 Mac OS X 10.11.6 Do you perhaps have a Chrome extension interfering with the behavior here somehow? Try again from an incognito window or fresh Chrome profile. Do you have another Mac you can test on, just to confirm that the issue is somehow confined to your specific device/account?
,
Dec 8 2016
,
Dec 8 2016
Still waiting on response. Test page works correctly for me on Mac.
,
Dec 13 2016
Able to reproduce this issue on Mac 10.11.6 using chrome reported version #54.0.2840.98 and latest canary #57.0.2949.0. Unable to reproduce on Linux and Windows. This is a non-regression issue as it is observed from M35 old builds. Hence, marking it as untriaged to get more inputs from dev team. Thanks...!!
,
Dec 13 2016
Tested on another Mac, in-private window and I am able to repro this. So I don't think it is related to installed extensions. Chrome: 54.0.2840.98 (64-bit) Mac: 10.10.2 (14C1514)
,
Dec 15 2016
I can certainly reproduce this on my desktop (no touchpad) but cannot on a laptop. Reproduced against 57.0.2952.0
,
Dec 15 2016
chongz@ can you investigate this?
,
Jan 6 2017
,
Jan 11 2018
Re-assigning to dtapuska@. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by ellyjo...@chromium.org
, Nov 29 2016Status: Untriaged (was: Unconfirmed)