Platform/Features/Full Screen APIs: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(template)
 
No edit summary
Line 7: Line 7:
|-
|-
<section begin="status" />
<section begin="status" />
| [[Feature Page Structure]]
| [[Platform/Features/Full Screen APIs|Full Screen APIs]]
| {{StatusHealthy|status=One or two sentence status report.}}
| {{StatusHealthy|status=Has proposal API}}
| YYYY-MM-DD
| None
| Owner Name
| Robert O'Callahan
<section end="status" />
<section end="status" />
|-
|-
Line 16: Line 16:


== Summary ==
== Summary ==
Very succinct (one or two line) summary of what this feature is all about.
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 ==
== Team ==
Who's working on this?
Who's working on this?


* '''Lead Developer''':
* '''Lead Developer''': Unassigned
* '''Product Manager''':
* '''Product Manager''': Chris Blizzard
* '''QA''':
* '''QA''': Unassigned
* '''UX''':
* '''UX''': Unassigned
* '''Security''':
* '''Security''': Unassigned
* Etc.


Team list should make it clear who to ask about what, and who to ping when they're needed.
Robert is the main contact right now.  He's written the original proposal.  It currently needs an owner.


== Release Requirements ==
== Release Requirements ==
Complete checklist of items that need to be satisfied before we can call this feature "done".
1. Code needs to written and tested.
2. Needs an early security review, both design and implementaiton.


== Next Steps ==
== Next Steps ==
Either the next set of tasks that need to happen to move this project along, or (ideally) the full list of project tasks/action items with things crossed off as they're finished.
Needs an engineer assigned to it.


== Related Bugs & Dependencies ==
== Related Bugs & Dependencies ==
Links to the feature tracking bug & other relevant bugs; links to related plans (test plan, product marketing plan, etc.); notes about things that depend on this, etc.
 
[https://bugzilla.mozilla.org/show_bug.cgi?id=545812 API for controlling fullscreen from content]


== Designs ==
== Designs ==
Any and all mockups, design specs, tech specs, etc.  Either inline or linked to.
 
[[Gecko:FullScreenAPI]]


== Goals/Use Cases ==
== Goals/Use Cases ==
The high level goals for the feature (which the release requirements checklist should fulfill).  These are the guiding light and overall vision for the feature.  Refer to this if there is confusion or are disputes about direction, designs, planning, etc.
This should be useful on any video site, HTML5 or not.  If video is involved it should allow for seamless transition from in-screen video to full screen video, including no audio skip.  It should also be useful for games and presentations.


== Non-Goals ==
== Non-Goals ==

Revision as of 12:04, 1 April 2011

Feature Status ETA Owner
Full Screen APIs Has proposal API None Robert O'Callahan

Summary

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

Who's working on this?

  • Lead Developer: Unassigned
  • Product Manager: Chris Blizzard
  • QA: Unassigned
  • UX: Unassigned
  • Security: Unassigned

Robert is the main contact right now. He's written the original proposal. It currently needs an owner.

Release Requirements

1. Code needs to written and tested. 2. Needs an early security review, both design and implementaiton.

Next Steps

Needs an engineer assigned to it.

Related Bugs & Dependencies

API for controlling fullscreen from content

Designs

Gecko:FullScreenAPI

Goals/Use Cases

This should be useful on any video site, HTML5 or not. If video is involved it should allow for seamless transition from in-screen video to full screen video, including no audio skip. It should also be useful for games and presentations.

Non-Goals

Things we are specifically not doing or building as part of this feature.

Other Documentation

Can include things like:

  • Competitive landscape
  • Research & references
  • Whatever else is useful to the project.

Legend (remove if you like)

  Healthy: feature is progressing as expected.
  Blocked: feature is currently blocked, but not yet at risk of missing this release.
  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.


Please remove this line and any non-relevant categories below. Add whatever other categories you feel are appropriate.

Retrieved from "https://wiki.mozilla.org/index.php?title=Platform/Features/Full_Screen_APIs&oldid=295910"