Closed Bug 2032302 Opened 23 days ago Closed 22 days ago

Ship Fullscreen keyboard lock to Desktop

Categories

(Core :: DOM: Core & HTML, task, P1)

task

Tracking

()

RESOLVED FIXED
151 Branch
Tracking Status
relnote-firefox --- ?
firefox151 + fixed

People

(Reporter: edgar, Assigned: avandolder)

References

(Blocks 3 open bugs)

Details

(Keywords: dev-doc-complete, webcompat:platform-bug)

Attachments

(1 file)

Enable dom.fullscreen.keyboard_lock.enabled by default.

Depends on: 2032306, 700123
Priority: -- → P1
Assignee: nobody → avandolder
Status: NEW → ASSIGNED
Summary: Ship Fullsceen keyboard lock → Ship Fullsceen keyboard lock to Desktop
Keywords: dev-doc-needed
Summary: Ship Fullsceen keyboard lock to Desktop → Ship Fullscreen keyboard lock to Desktop
Depends on: 2032718
Depends on: 2032647
Status: ASSIGNED → RESOLVED
Closed: 22 days ago
Resolution: --- → FIXED
Target Milestone: --- → 151 Branch
No longer depends on: 2032647
No longer depends on: 2032507

Could you consider nominating this for a release note? (Process info)

Flags: needinfo?(avandolder)

Release Note Request (optional, but appreciated)
[Why is this notable]: Enables the new Fullscreen Keyboard Lock API on all channels
[Affects Firefox for Android]: No, the API is disabled on Android
[Suggested wording]: The new Fullscreen Keyboard Lock API adds an optional argument to requestFullscreen that allows websites to request that while fullscreen, pressing the Escape key will no longer exit fullscreen (instead a long-press is required), and certain formerly-reserved browser hotkeys are allowed to be default-prevented.
[Links (documentation, blog post, etc)]: https://github.com/whatwg/fullscreen/pull/232

relnote-firefox: --- → ?
Flags: needinfo?(avandolder)

Thanks, added to the Fx151 nightly release notes, please allow 30 minutes for the site to update.
Keeping the relnote-firefox flag as ? to keep it on the radar for inclusion in the final Fx151 release notes.

QA Whiteboard: [qa-triage-done-c152/b151]

FF151 MDN work for this can be tracked in https://github.com/mdn/content/issues/43868

This is essentially done - waiting on browser compatibility data and docs reviews to go through.
Note that at least a little more work will likely be required when the spec merges to update the compatibility data, and possibly the docs, depending on how it changes.

How are they related to this one? They don't use keyboard lock?

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: