Open Bug 746437 Opened 12 years ago Updated 1 year ago
[meta] Update fullscreen API to match latest draft spec
The W3 fullscreen spec  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.  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.
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!
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.
Good to hear! Thanks.
OS: Windows 7 → All
Hardware: x86_64 → All
Version: 11 Branch → Trunk
Current do not support the non-prefix fullscreen API.
Summary: Update fullscreen API to match latest draft spec → [meta] Update fullscreen API to match latest draft spec
See Also: → https://webcompat.com/issues/16412
Webcompat Priority: ? → ---
You need to log in before you can comment on or make changes to this bug.