Closed Bug 1834542 Opened 3 years ago Closed 3 years ago

Requesting fullscreen in A/B/A element order doesn't match the spec

Categories

(Core :: DOM: Core & HTML, defect)

defect

Tracking

()

RESOLVED DUPLICATE of bug 1832837

People

(Reporter: foolip, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/113.0.0.0 Safari/537.36

Steps to reproduce:

A test for this was added in https://github.com/web-platform-tests/wpt/pull/39828, results at https://wpt.fyi/results/fullscreen/api/fullscreen-reordering.html.

This has long been required by the spec, but got renewed attention with https://github.com/whatwg/fullscreen/pull/223.

I did some manual testing in https://github.com/whatwg/fullscreen/pull/223#issuecomment-1522928629.

Actual results:

The test doesn't work because Firefox still has a hierarchy requirement for the Fullscreen API, failing because A and B are siblings in the DOM.

Expected results:

Element A should end up fullscreen.

The Bugbug bot thinks this bug should belong to the 'Core::DOM: Core & HTML' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → DOM: Core & HTML
Product: Firefox → Core

This should be fixed by bug 1832837.

Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Duplicate of bug: 1832837
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.