Platform/Features/Full Screen APIs: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 31: Line 31:


== Release Requirements ==
== Release Requirements ==
* Code needs to written and tested.
* Code needs to written and tested (Karl)
* Needs more spec work.
* Needs more spec work (Tantek)
* Needs an early security review, both design and implementaton.
* Needs an early security review, both design and implementaton (TBA)


== Next Steps ==
== Next Steps ==

Revision as of 00:14, 8 April 2011

Feature Status ETA Owner
Full Screen APIs Has owner, needs some more spec work and impl (Karl Tomlinson & Tantek) Unknown Karl Tomlinson

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: Karl Tomlinson
  • Product Manager: Chris Blizzard
  • Standards: Tantek
  • QA: Unassigned
  • UX: Unassigned
  • Security: Unassigned

Robert wrote the original proposal. Karl has signed up to build it. Tantek will help with standards.

Release Requirements

  • Code needs to written and tested (Karl)
  • Needs more spec work (Tantek)
  • Needs an early security review, both design and implementaton (TBA)

Next Steps

Karl and Roc need to communicate about details and work with Tantek on spec details.

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.