What is the issue with the Fullscreen API Standard?
Both Safari and Chrome ship "implicit keyboard lock" on fullscreen, meaning fullscreen session can access more keys without any extra API.
Try: data:text/html,<style>::backdrop { background-color: gray }</style><button onclick="document.body.requestFullscreen()">Fullscreen</button><p id=log></p><script>onkeydown = ev => { ev.preventDefault(); log.prepend(ev.key, document.createElement("br")) }</script>
Try Control+T or Meta+T to open a new tab for example. Without fullscreen the page cannot capture the relevant keyboard event, with fullscreen it can.
This behavior should be specified somewhere. (Unless implementors regret and want to change this, that is.)
What is the issue with the Fullscreen API Standard?
Both Safari and Chrome ship "implicit keyboard lock" on fullscreen, meaning fullscreen session can access more keys without any extra API.
Try:
data:text/html,<style>::backdrop { background-color: gray }</style><button onclick="document.body.requestFullscreen()">Fullscreen</button><p id=log></p><script>onkeydown = ev => { ev.preventDefault(); log.prepend(ev.key, document.createElement("br")) }</script>Try Control+T or Meta+T to open a new tab for example. Without fullscreen the page cannot capture the relevant keyboard event, with fullscreen it can.
This behavior should be specified somewhere. (Unless implementors regret and want to change this, that is.)