Platform/Features/Full Screen APIs: Difference between revisions

Latest revision as of 16:20, 14 November 2011

Please use "Edit with form" above to edit this page.

Status

Full Screen APIs
Stage	Landed
Status	Complete
Release target	Firefox 10
Health	OK
Status note	This is tracking to release in Firefox 10.

{{#set:Feature name=Full Screen APIs

|Feature stage=Landed |Feature status=Complete |Feature version=Firefox 10 |Feature health=OK |Feature status note=This is tracking to release in Firefox 10. }}

Team

Product manager	Chris Blizzard
Directly Responsible Individual	Martin Best
Lead engineer	Chris Pearce
Security lead	Curtis Koenig
Privacy lead	`
Localization lead	`
Accessibility lead	`
QA lead	Paul Silaghi
UX lead	`
Product marketing lead	`
Operations lead	`
Additional members	Tantek (standards)

{{#set:Feature product manager=Chris Blizzard

|Feature feature manager=Martin Best |Feature lead engineer=Chris Pearce |Feature security lead=Curtis Koenig |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=Paul Silaghi |Feature ux lead=` |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=Tantek (standards) }}

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

` {{#set:Feature open issues and risks=` |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. |Feature dependencies=` |Feature requirements=` |Feature non-goals=` |Feature functional spec=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/ |Feature ux design=` |Feature implementation plan=` |Feature security review=* There are security implications to this feature, which is why it needs a design review. |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=* API for controlling fullscreen from content |Feature landing criteria=` }}

Feature details

Priority	P1
Rank	999
Theme / Goal	`
Roadmap	Platform
Secondary roadmap	`
Feature list	Platform
Project	`
Engineering team	Layout

{{#set:Feature priority=P1

|Feature rank=999 |Feature theme=` |Feature roadmap=Platform |Feature secondary roadmap=` |Feature list=Platform |Feature project=` |Feature engineering team=Layout }}

Team status notes

	status	notes
Products	`	`
Engineering	`	`
Security	sec-review-complete	Completed: 2011.10.03 Notes
Privacy	`	`
Localization	`	`
Accessibility	`	`
Quality assurance	`	`
User experience	`	Test Plan
Product marketing	`	`
Operations	`	`

{{#set:Feature products status=`

|Feature products notes=` |Feature engineering status=` |Feature engineering notes=` |Feature security status=sec-review-complete |Feature security health=OK |Feature security notes=Completed: 2011.10.03 Notes |Feature privacy status=` |Feature privacy notes=` |Feature localization status=` |Feature localization notes=` |Feature accessibility status=` |Feature accessibility notes=` |Feature qa status=` |Feature qa notes=` |Feature ux status=` |Feature ux notes=Test Plan |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}

@@ Line 1: / Line 1: @@
-{| class="fullwidth-table"
+{{FeatureStatus
-|-
+|Feature name=Full Screen APIs
-| style="font-weight: bold; background: #DDD;" | Feature
+|Feature stage=Landed
-| style="font-weight: bold; background: #DDD;" | Status
+|Feature status=Complete
-| style="font-weight: bold; background: #DDD;" | ETA
+|Feature version=Firefox 10
-| style="font-weight: bold; background: #DDD;" | Owner
+|Feature health=OK
-|-
+|Feature status note=This is tracking to release in Firefox 10.
-<section begin="status" />
+}}
-| [[Platform/Features/Full Screen APIs|Full Screen APIs]]
+{{FeatureTeam
-| {{StatusHealthy|status=Has owner, needs some more spec work (tantek) impl (karlt,cpearce) and security design review (curtis)}}
+|Feature product manager=Chris Blizzard
-| Unknown
+|Feature feature manager=Martin Best
-| Karl Tomlinson, Chris Pearce
+|Feature lead engineer=Chris Pearce
-<section end="status" />
+|Feature security lead=Curtis Koenig
-|-
+|Feature qa lead=Paul Silaghi
-|}
+|Feature additional members=Tantek (standards)
+}}
+{{FeaturePageBody
+|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.
+|Feature functional spec=Firefox: [[Gecko:FullScreenAPI]]
-== Summary ==
+Chrome extensions: http://peter.sh/2011/01/javascript-full-screen-api-navigation-timing-and-repeating-css-gradients/
-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.
-== Team ==
+Checkin in WebKit: http://trac.webkit.org/changeset/92576
-Who's working on this?
-* '''Lead Developer''': Karl Tomlinson
+Chrome review: http://codereview.chromium.org/7461059/
-* '''Developer''': Chris Pearce
+|Feature security review=* There are security implications to this feature, which is why it needs a design review.
-* '''Product Manager''': Chris Blizzard
+|Feature implementation notes=* [https://bugzilla.mozilla.org/show_bug.cgi?id=545812 API for controlling fullscreen from content]
-* '''Standards''': Tantek
+}}
-* '''QA''': AndreiD
+{{FeatureInfo
-* '''UX''': Unassigned
+|Feature priority=P1
-* '''Security (Design)''': Curtis Koenig
+|Feature roadmap=Platform
+|Feature list=Platform
-Robert wrote the original proposal.  Karl has signed up to build it.  Tantek will help with standards.
+|Feature engineering team=Layout
+}}
-== Release Requirements ==
+{{FeatureTeamStatus
-* Code needs to written and tested (Karl, Chris P.)
+|Feature security status=sec-review-complete
-* Needs more spec work (Tantek)
+|Feature security health=OK
-* Needs an early security review, both design and implementaton (TBA)
+|Feature security notes=Completed: 2011.10.03 [[Security/Reviews/Firefox10/CodeEditor/FullScreenAPI|Notes]]
+|Feature ux notes=[https://wiki.mozilla.org/Platform/Features/Full_Screen_APIs/TestPlan Test Plan]
-== Next Steps ==
+}}
-Karl and Roc need to communicate about details and work with Tantek on spec details.  Curtis will need to figure out the a security design review.
-== Related Bugs & Dependencies ==
-[https://bugzilla.mozilla.org/show_bug.cgi?id=545812 API for controlling fullscreen from content]
-== Designs ==
-[[Gecko:FullScreenAPI]]
-== Goals/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.
-There are security implications to this feature, which is why it needs a design review.
-== Non-Goals ==
-None listed.
-== Other Documentation ==
-None listed.
-== Legend (remove if you like) ==
-{| class="fullwidth-table"
-|-
-| {{StatusHealthy|status=&nbsp;}}
-| Healthy: feature is progressing as expected.
-|-
-| {{StatusBlocked|status=&nbsp;}}
-| Blocked: feature is currently blocked, but not yet at risk of missing this release.
-|-
-| {{StatusAtRisk|status=&nbsp;}}
-| At Risk: feature is at risk of missing this release.
-|-
-| '''ETA'''
-| Estimated date for completion of the current feature task. Overall ETA for the feature is the product release date.
-|}
-__NOTOC__
-Please remove this line and any non-relevant categories below.  Add whatever other categories you feel are appropriate.
-[[Category:Features]]
-[[Category:Firefox]]
-[[Category:Performance]]
-[[Category:Polish]]
-[[Category:Priority 1]]
-[[Category:Priority 2]]
-[[Category:Priority 3]]
-[[Category:Unprioritized]]