Platform/Features/Full Screen APIs: Difference between revisions

Platform/Features/Full Screen APIs (view source)

Revision as of 02:14, 8 November 2011

515 bytes removed , 8 November 2011

no edit summary

Cpearce

Confirmed users

91

edits

@@ Line 2: / Line 2: @@
 |Feature name=Full Screen APIs
 |Feature stage=Landed
-|Feature status=In progress
+|Feature status=Complete
 |Feature version=Firefox 10
-|Feature health=At risk
+|Feature health=OK
-|Feature status note=This is tracking to release in Firefox 10.  A dependencies is currently considered risky to land for 10 without regressions.  See risk section for details.
+|Feature status note=This is tracking to release in Firefox 10.
 }}
 {{FeatureTeam
@@ Line 16: / Line 16: @@
 }}
 {{FeaturePageBody
-|Feature open issues and risks=- This requires the following [https://bugzilla.mozilla.org/show_bug.cgi?id=90268 90268] to be fixed in order to release. (The dependance is linked via bug [https://bugzilla.mozilla.org/show_bug.cgi?id=684618 684618]).  The last update was that landing the dependency by 10 would be risky and would likely include regressions that would need to be fixed quickly.
 |Feature overview=This feature allows you to build a web application that runs full screen.  This includes any HTML element so you can build full screen games, full interactive video experiences, presentation software or anything else that should dominate the experience.
 |Feature users and use cases=This feature should allow any app to create a full screen HTML-based experience.  This means that an app should be able to create a full screen context of an element.  That element can contain HTML, video, canvas or even flash.  This should be useful for games, presentations or video experiences.