Platform/Features/Full Screen APIs/TestPlan: Difference between revisions
< Platform | Features | Full Screen APIs
Jump to navigation
Jump to search
Paul.silaghi (talk | contribs) |
Paul.silaghi (talk | contribs) |
||
Line 35: | Line 35: | ||
;Edge Cases | ;Edge Cases | ||
*Also, the | *Also, the elements should run without problems in full screen mode: | ||
** | **Multiple tabs are loaded<br> | ||
** | **Multiple browser windows are available<br> | ||
**Browser is in Panorama mode<br> | |||
**Heavy user profile is loaded (large history, multiple bookmarks, user settings, tabs, add-ons)<br> | |||
**Private browsing is on<br> | |||
== Test Cases == | == Test Cases == |
Revision as of 16:15, 14 November 2011
Full Screen APIs
Feature | Status | Lead Engineer | QA Lead | Status |
Full Screen APIs | Landed in Firefox/10.0a2 | Chris Pearce | Paul Silaghi | Complete |
Summary
- This feature enables developers to make an arbitrary HTML element "full-screen", hiding the browser's UI and stretching the element to encompass the entire screen
- Useful for HTML5 video and games.
- This feature is available starting Firefox/10.0a2
Reference
- Design and infrastructure:
- Bug 545812 - API for controlling fullscreen from content
Use Cases to Test
- Basic Functional Testing
- Open the demo page and check if HTML elements can go in full screen mode.
- Edge Cases
- Also, the elements should run without problems in full screen mode:
- Multiple tabs are loaded
- Multiple browser windows are available
- Browser is in Panorama mode
- Heavy user profile is loaded (large history, multiple bookmarks, user settings, tabs, add-ons)
- Private browsing is on
- Multiple tabs are loaded
Test Cases
- A list of test cases for this feature can be found here: Test Cases
Important bugs
- Bug 545812 - API for controlling fullscreen from content