Open
Bug 1494236
Opened 6 years ago
Updated 2 years ago
[meta] Fix web-platform test failures of Fullscreen API
Categories
(Core :: DOM: Core & HTML, enhancement, P3)
Core
DOM: Core & HTML
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox64 | --- | affected |
People
(Reporter: xidorn, Unassigned)
References
(Depends on 5 open bugs, Blocks 1 open bug)
Details
(Keywords: meta)
Most of the tests are currently manual tests due to lack of user interaction support.
Failures on manual tests are:
exitFullscreen should be async (bug 1492732):
* fullscreen/api/document-exit-fullscreen-nested-manual.html
resize event alignment (bug 1492748):
* fullscreen/api/document-exit-fullscreen-timing-manual.html
* fullscreen/api/element-request-fullscreen-timing-manual.html
hierarchy restriction ( whatwg/fullscreen#140 ):
* fullscreen/api/element-ready-check-fullscreen-element-sibling-manual.html
* fullscreen/api/element-request-fullscreen-non-top-manual.html
* fullscreen/api/element-request-fullscreen-two-elements-manual.html
<dialog> support (bug 840640):
* fullscreen/api/element-request-fullscreen-dialog-manual.html
remove element cause completely exit fullscreen (we don't have consensus here):
* fullscreen/model/remove-last-manual.html
There are several tests affected by bug 1493878 which caused them to timeout. The list above are the situation with that issue worked around in web-platform-tests/wpt#13102.
In addition to manual tests, there are two automatic tests are still failing:
FullscreenOptions with navigationUI (bug 1492081):
* fullscreen/api/element-request-fullscreen-options.html
Remove prefixed Fullscreen API (bug 1249225):
* fullscreen/api/historical.html
Comment 2•6 years ago
|
||
We draw these things differently on different OSes. I'm not sure this is a bug and I'm not sure where it should live ...
Component: DOM: Core & HTML → Widget: Win32
Comment 3•6 years ago
|
||
Sorry, comment 2 was for another bug ...
Component: Widget: Win32 → DOM: Core & HTML
Priority: -- → P3
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•