canmove, Confirmed users
1,577
edits
Platform/Features/Full Screen APIs: Difference between revisions
Jump to navigation
Jump to search
Platform/Features/Full Screen APIs (view source)
Revision as of 22:36, 19 August 2011
, 19 August 2011no edit summary
No edit summary |
No edit summary |
||
| Line 19: | Line 19: | ||
|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. | |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. | ||
|Feature functional spec=* [[Gecko:FullScreenAPI]] | |Feature functional spec=* [[Gecko:FullScreenAPI]] | ||
Chrome extensions: http://peter.sh/2011/01/javascript-full-screen-api-navigation-timing-and-repeating-css-gradients/ | |||
Checkin in WebKit: http://trac.webkit.org/changeset/92576 | |||
|Feature security review=* There are security implications to this feature, which is why it needs a design review. | |Feature security review=* There are security implications to this feature, which is why it needs a design review. | ||
|Feature implementation notes=* [https://bugzilla.mozilla.org/show_bug.cgi?id=545812 API for controlling fullscreen from content] | |Feature implementation notes=* [https://bugzilla.mozilla.org/show_bug.cgi?id=545812 API for controlling fullscreen from content] | ||