Mobile/Projects/HTML5 compatibility: Difference between revisions
Jump to navigation
Jump to search
Full Query
m (→Tracking) |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
== Tracking == | == Tracking == | ||
;Fx21 | |||
<onlyinclude><bugzilla> | |||
{ | |||
"bug_id": "791654", | |||
"include_fields": "id, priority, summary, status, assigned_to", | |||
"order": "bug_id" | |||
} | |||
</bugzilla></onlyinclude> | |||
;Fx23 | ;Fx23 | ||
snippets from previous status | snippets from previous status | ||
Latest revision as of 16:29, 18 April 2013
Tracking
- Fx21
| ID | Priority | Summary | Status | Assigned to |
|---|---|---|---|---|
| 791654 | -- | Add save file as to the html5 player context menu | VERIFIED | heyjinsu |
1 Total; 0 Open (0%); 0 Resolved (0%); 1 Verified (100%);
- Fx23
snippets from previous status
- Two HTML5 features landed: HTML5 <input type="range"> and Web Notifications. We got a bump on html5test.com for the range control, but the notifications are blocked on bad testing code. David Baron has a pull request to fix html5test.'
- Moar HTML5 APIs (Web Audio): Web Audio was enabled on Nightlies. This bumps our HTML5 score to 431
Goals
- Increases our scores when run on the standard HTML5 compatibility tests
User stories
- As a potential partner, when I run Fennec using the HTML5 compatibility tests, I am ahead or on par with Chrome, Opera and Dolphin so I can move on to the next phase of discussions.
Quality criteria
- User stories are satisfied
- Specifications are met