Chrome Version: (copy from chrome://version)
OS: (e.g. Win7, OSX 10.9.5, etc...)

What steps will reproduce the problem?
I have a minimum repro case at jsbin.com/fadepox.

(1) Resize your Chrome window to a smaller size.
(2) Request pointer lock and then full screen. (In jsbin.com/fadepox, click the 'LOCK POINTER, FULLSCREEN' button.)
(3) Move the mouse around.

(1) Resize your Chrome window to a smaller size.
(2) Open the element inspection tool.
(3) Request full screen and then pointer lock. (In jsbin.com/fadepox, click the 'FULLSCREEN, LOCK POINTER' button.)
(4) Move the mouse around.

What is the expected result?

mousemove events should provide movementX and movementY values that match the user's motion. (The box on the jsbin should move around with mouse movements.)

What happens instead?

mousemove events sometimes provide a 0 instead of real movementX or movementY values. (The colored box on the jsbin.com/fadepox looks as though it is constrained to a box smaller than the screen. movementX and movementY are are also logged to the console in the jsbin, and will sometimes present a 0 in the movementX or movementY  when the mouse is moved in those directions.)

Please use labels and text to provide additional information.


For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.

 

Chrome Version: (copy from 64.0.3282.167), but also with some versions of 63 and 65
OS: Win7

What steps will reproduce the problem?
I have a minimum repro case at jsbin.com/fadepox.

(1) Resize your Chrome window to a smaller size.
(2) Request pointer lock and then full screen. (In jsbin.com/fadepox, click the 'LOCK POINTER, FULLSCREEN' button.)
(3) Move the mouse around.

(1) Resize your Chrome window to a smaller size.
(2) Open the element inspection tool.
(3) Request full screen and then pointer lock. (In jsbin.com/fadepox, click the 'FULLSCREEN, LOCK POINTER' button.)
(4) Move the mouse around.

What is the expected result?

mousemove events should provide movementX and movementY values that match the user's motion. (The box on the jsbin should move around with mouse movements.)

What happens instead?

mousemove events sometimes provide a 0 instead of real movementX or movementY values. (The colored box on the jsbin.com/fadepox looks as though it is constrained to a box smaller than the screen. movementX and movementY are are also logged to the console in the jsbin, and will sometimes present a 0 in the movementX or movementY  when the mouse is moved in those directions.)

Please use labels and text to provide additional information.


For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.

 

Chrome Version: (copy from 64.0.3282.167), but also with some versions of 63 and 65
OS: Win10

What steps will reproduce the problem?
I have a minimum repro case at jsbin.com/fadepox.

(1) Resize your Chrome window to a smaller size.
(2) Request pointer lock and then full screen. (In jsbin.com/fadepox, click the 'LOCK POINTER, FULLSCREEN' button.)
(3) Move the mouse around.

(1) Resize your Chrome window to a smaller size.
(2) Open the element inspection tool.
(3) Request full screen and then pointer lock. (In jsbin.com/fadepox, click the 'FULLSCREEN, LOCK POINTER' button.)
(4) Move the mouse around.

What is the expected result?

mousemove events should provide movementX and movementY values that match the user's motion. (The box on the jsbin should move around with mouse movements.)

What happens instead?

mousemove events sometimes provide a 0 instead of real movementX or movementY values. (The colored box on the jsbin.com/fadepox looks as though it is constrained to a box smaller than the screen. movementX and movementY are are also logged to the console in the jsbin, and will sometimes present a 0 in the movementX or movementY  when the mouse is moved in those directions.)

Please use labels and text to provide additional information.


For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.