CrOS screen capture cursor invisible when PointerLock is requested |
||
Issue descriptionChrome OS Version: 70.0.3511.0 and earlier Steps To Reproduce: (1) navigate to pointer lock demo page (2) click canvas (black area) to request pointer lock (3) Press Ctrl-Shift-Windows to trigger screen capture Expected Result: A crosshair cursor guides selection of capture area Actual Result: No crosshair cursor until button click to select starting point. How frequently does this problem reproduce? (Always, sometimes, hard to reproduce?) Always What is the impact to the user, and is there a workaround? If so, what is it? Please provide any additional information below. Attach a screen shot or log if possible. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Aug 17
We own pointerlock. Ella has been working on the related issues recently. Francis is releasing the pointerlock a reasonable behavior? We have some inconsistencies on Mac as well when we are in pointerlock and Cmd+shift+4 will create an area selection. Firefox doesn't behave very well on Mac either. I guess this behavior is mainly undefined from the spec point of view.
,
Aug 17
For our app, we detect loss of pointerlock and pops up a dialog to request pointerlock again. So it would be a little odd. Having said that, this is not really an important usecase for us. Reporting this mainly as an FYI. |
||
►
Sign in to add a comment |
||
Comment 1 by bokan@chromium.org
, Aug 17Owner: nzolghadr@chromium.org
Status: Assigned (was: Unconfirmed)