Open
Bug 746437
Opened 13 years ago
Updated 2 years ago
[meta] Update fullscreen API to match latest draft spec
Categories
(Core :: DOM: Core & HTML, task, P2)
Core
DOM: Core & HTML
Tracking
()
NEW
People
(Reporter: cpearce, Unassigned)
References
(Depends on 5 open bugs, Blocks 2 open bugs)
Details
(Keywords: meta)
The W3 fullscreen spec [1] has changed again. There's now the concept of a backdrop, and the CSS pseudoclass rules have changed, and there's a new stacking layer concept. We should decide whether we object, and then implement it or kick up a fuss.
[1] http://dvcs.w3.org/hg/fullscreen/raw-file/tip/Overview.html
I can't think of a good reason to not implement it as-is.
Comment 2•11 years ago
|
||
Hi all. I'm aiming to implement the latest Fullscreen spec in Blink, so I'm curious about whether Firefox folks feel positively about the spec:
http://fullscreen.spec.whatwg.org/
I think not much has changed in the spec since the last comment (the version discussed seems to be https://dvcs.w3.org/hg/fullscreen/raw-file/e1223b9b491d/Overview.html), but it's been a while.
The Blink bug is:
https://code.google.com/p/chromium/issues/detail?id=240576
Thanks for any information!
Reporter | ||
Comment 3•11 years ago
|
||
Thanks for checking in Matt! I did our initial fullscreen API implementation. I think we're all happy with the current spec, and would be happy for it to become the standard.
Comment 4•11 years ago
|
||
Good to hear! Thanks.
Blocks: 888979
Updated•10 years ago
|
OS: Windows 7 → All
Hardware: x86_64 → All
Version: 11 Branch → Trunk
Updated•10 years ago
|
Depends on: ::backdrop
Updated•9 years ago
|
Blocks: fullscreen-api
Updated•8 years ago
|
Keywords: meta
Summary: Update fullscreen API to match latest draft spec → [meta] Update fullscreen API to match latest draft spec
Updated•6 years ago
|
Priority: -- → P2
Updated•6 years ago
|
See Also: → https://webcompat.com/issues/16412
Updated•6 years ago
|
Type: defect → task
Updated•3 years ago
|
Webcompat Priority: --- → ?
Comment 6•3 years ago
|
||
Removing the webcompat-priority flag here. Having the priority on a metabug isn't too useful - we should track and triage individual issues instead if specific issues show up.
Webcompat Priority: ? → ---
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•