Platform/Features/Full Screen APIs

Status

Team

Open issues/risks

`

Stage 1: Definition

1. 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.

2. Users & 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.

3. Dependencies

`

4. Requirements

`

Non-goals

`

Stage 2: Design

5. Functional specification

Firefox: 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

Chrome review: http://codereview.chromium.org/7461059/

6. User experience design

`

Stage 3: Planning

7. Implementation plan

`

8. Reviews

Security review

• There are security implications to this feature, which is why it needs a design review.

Privacy review

`

Localization review

`

Accessibility

`

Quality Assurance review

`

Operations review

`

Stage 4: Development

9. Implementation

• API for controlling fullscreen from content

Stage 5: Release

10. Landing criteria

`

Feature details

Team status notes