Platform/Features/Full Screen APIs/TestPlan: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "= Lessen App Update Displayed UI = {| class="fullwidth-table" |- | Feature | Status | Lead Engineer | QA Lead | Status |- | Lessen App Update Displayed UI | {{StatusHealth...")
 
Line 1: Line 1:
= Lessen App Update Displayed UI =
= Full Screen APIs =


{| class="fullwidth-table"
{| class="fullwidth-table"
Line 9: Line 9:
| Status
| Status
|-
|-
| Lessen App Update Displayed UI
| Full Screen APIs
| {{StatusHealthy|status=Landed in Firefox 8}}  
| {{StatusHealthy|status=Landed in Firefox/10.0a2}}  
| Tim Taubert
| Chris Pearce
| PaulS
| Paul Silaghi
| {{StatusHealthy|status=Complete}}<br>
| {{StatusHealthy|status=Complete}}<br>
|}
|}
Line 18: Line 18:
== Summary  ==
== Summary  ==


*A notification that there is an update downloaded/ready to install and Firefox needs to be restarted to apply the update is displayed 24 hours after an update has been downloaded.
*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
*This changes the old notification time from 12 to 24 hours.  
*Useful for HTML5 video and games.
*This feature is available starting Firefox 8 Beta
*This feature is available starting Firefox/10.0a2


== Reference  ==
== Reference  ==


*Design and infrastructure:  
*Design and infrastructure:  
**[https://bugzilla.mozilla.org/show_bug.cgi?id=659425 Bug 659425] - get average session length from crash stats and Test Pilot studies
**[https://bugzilla.mozilla.org/show_bug.cgi?id=545812 Bug 545812] - API for controlling fullscreen from content
**[https://bugzilla.mozilla.org/show_bug.cgi?id=657472 Bug 657472] - 'Tune' the time to wait before displaying the update been downloaded / restart notification and provide ability to override in the update xml


== Use Cases to Test  ==
== Use Cases to Test  ==
Line 32: Line 31:
;Basic Functional Testing
;Basic Functional Testing


*Steps to verify:  
*Open the [http://pearce.org.nz/full-screen/ demo page] and check if HTML elements can go in full screen mode.
**Install a version of Firefox which requires updates
**Launch Firefox<br>
**Go to Help/About Firefox<br>
**After the new version is downloaded, simply close the About dialog and leave Firefox running for at least 24 hours<br>
*Expected result:
**After 24 hours a notification to restart Firefox in order to apply the update should be displayed<br>


;Edge Cases
;Edge Cases


*Also, the notification should occur with no problem after 24 hours if:<br>
*Also, the following elements should run without problems in full screen mode:
**Multiple tabs are loaded<br>
**flash animations
**Multiple browser windows are available<br>
**images
**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  ==
Line 55: Line 45:
== Important bugs  ==
== Important bugs  ==


*[https://bugzilla.mozilla.org/show_bug.cgi?id=659425 bug 659425] - get average session length from crash stats and Test Pilot studies
*[https://bugzilla.mozilla.org/show_bug.cgi?id=545812 Bug 545812] - API for controlling fullscreen from content
*[https://bugzilla.mozilla.org/show_bug.cgi?id=657472 bug 657472] - 'Tune' the time to wait before displaying the update been downloaded / restart notification and provide ability to override in the update xml<br>
 
<br>

Revision as of 15:58, 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 following elements should run without problems in full screen mode:
    • flash animations
    • images

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
Retrieved from "https://wiki.mozilla.org/index.php?title=Platform/Features/Full_Screen_APIs/TestPlan&oldid=369186"