FF151 Fullscreen Keyboard Lock API#29548
Open
hamishwillee wants to merge 1 commit intomdn:mainfrom
Open
Conversation
8 tasks
Contributor
|
Tip: Review these changes grouped by change (recommended for most PRs), or grouped by feature (for large PRs). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
FF151 supports the Fullscreen Keyboard Lock API in https://bugzilla.mozilla.org/show_bug.cgi?id=2032302 (implementation in https://bugzilla.mozilla.org/show_bug.cgi?id=700123).
This is the addition of a
keyboardLockoption (to theoptionsparameter) that can take the valuesnoneorbrowserto theElement.requestFullScreen(). This is also supported by Safari 26.4 (search keyboard lock) but not yet by Chrome (https://issues.chromium.org/issues/505427218).Safari has an extra option
systemthat means the same asnone(does nothing). I have not captured that because it isn't in the prospective spec.The spec for this has not landed, but seems to be heading towards some kind of agreement as we speak. whatwg/fullscreen#232
Given that I gave marked this non-standard - and the fact is I am not sure yet exactly what it will end up doing. I.e whether anything that counts as "compatibility" will change.
Related docs work can be tracked in mdn/content#43868