You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would expect that the behavior of the Esc key changes, where I would now need to press and hold Esc for a few seconds before fullscreen is actually exited. As described here: https://developer.chrome.com/blog/better-full-screen-mode/
I imagine the same behavior change should hold for when requestPointerLock() is used.
Actual Behavior
When the Esc key is pressed after bringing an element to fullscreen, it ALWAYS exits fullscreen immediately, even when used in combination with keyboard.lock() API.
Testcase Gist URL
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered:
Preflight Checklist
Electron Version
27.0.2
What operating system are you using?
Windows
Operating System Version
Windows 10 Pro version 22H2
What arch are you using?
x64
Last Known Working Electron version
No response
Expected Behavior
When an element is brought to fullscreen with:
elem.requestFullscreen()
and an event listener exists like:
I would expect that the behavior of the Esc key changes, where I would now need to press and hold Esc for a few seconds before fullscreen is actually exited. As described here: https://developer.chrome.com/blog/better-full-screen-mode/
I imagine the same behavior change should hold for when requestPointerLock() is used.
Actual Behavior
When the Esc key is pressed after bringing an element to fullscreen, it ALWAYS exits fullscreen immediately, even when used in combination with keyboard.lock() API.
Testcase Gist URL
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: