- From: Mustaq Ahmed <notifications@github.com>
- Date: Fri, 24 Apr 2020 10:57:51 -0700
- To: whatwg/fullscreen <fullscreen@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 24 April 2020 17:58:03 UTC
In Chrome, PointerLock is [gated](https://source.chromium.org/chromium/chromium/src/+/master:content/renderer/mouse_lock_dispatcher.h;drc=d6cc9b864d0a7340d420a7a39528041680614b18;l=37-39?originalUrl=https:%2F%2Fcs.chromium.org%2F) by transient user activation but doesn't consume it; this is unlike Fullscreen which actually consumes it. So if a click handler calls pointerlock then fullscreen, it would work, but not the other way around. @EdgarChen Does it match your observation? We started consuming at fullscreen request last year, don't recall any compat issues. I couldn't confirm if Chrome may have pointerLock + fullscreen special handling. @NavidZ might know. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/fullscreen/issues/152#issuecomment-619162017
Received on Friday, 24 April 2020 17:58:03 UTC