Platform/Features/Full Screen APIs: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 24: Line 24:
* '''Product Manager''': Chris Blizzard
* '''Product Manager''': Chris Blizzard
* '''Standards''': Tantek
* '''Standards''': Tantek
* '''QA''': Unassigned
* '''QA''': AndreiD
* '''UX''': Unassigned
* '''UX''': Unassigned
* '''Security (Design)''': Curtis Koenig
* '''Security (Design)''': Curtis Koenig

Revision as of 14:52, 15 June 2011

Feature Status ETA Owner
Full Screen APIs Has owner, needs some more spec work (tantek) impl (karlt) and security design review (curtis) 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: AndreiD
  • UX: Unassigned
  • Security (Design): Curtis Koenig

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. Curtis will need to figure out the a security design review.

Related Bugs & Dependencies

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)

  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.allizom.org/index.php?title=Platform/Features/Full_Screen_APIs&oldid=319327"