web-platform-tests / web-platform-tests/interop
Keyboard Lock in requestFullscreen
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 524
- Forks
- 35
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 10
Description
Description
The Fullscreen Keyboard Lock API adds an optional argument to requestFullscreen that allows websites to request that while they are in fullscreen, pressing the Escape key no longer exits fullscreen, and certain formerly-reserved browser hotkeys are allowed to be default-prevented.
This is common in gaming use cases. Whilst different browsers support similar functionality, there currently isn't universal alignment around the standard, making it harder for developers to produce interoperable pages without browser-specific codepaths.
Specification
https://fullscreen.spec.whatwg.org/#keyboard-locking
web-feature
No response
Test Links
https://wpt.fyi/results/fullscreen/api?label=master&label=experimental&aligned&q=keyboard-lock
Additional Signals
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the Keyboard Locking section of the Fullscreen specification and reviewing the existing fullscreen/api results linked on wpt.fyi. Compare current coverage and browser behavior, using the Mozilla Bugzilla report for context. Done means the relevant Web Platform Tests represent the specified requestFullscreen behavior and expose interoperability gaps clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing-qa, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100