Platform/HTML5 parser tasks: Difference between revisions
< Platform
Jump to navigation
Jump to search
Line 11: | Line 11: | ||
****Preliminary layout patch exists. Waiting for the CSS WG to approve the solution or propose another solution. | ****Preliminary layout patch exists. Waiting for the CSS WG to approve the solution or propose another solution. | ||
*Reviews on patches | *Reviews on patches | ||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=552938 552938] Implement the SVG load event in text/html (jwatt) | |||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=552908 552908] Implement spec changes to SVG </a> and </font> handling (sicking) | |||
***The patch improvises around spec bugs. Let's adjust things later when Hixie fixes the spec. | |||
*Security review. | *Security review. | ||
** Talked to dveditz about how to do the security review for the HTML5 parser, and it's not clear what the best format for the review would be. But we did decide that it's not something we need to do before turning the parser on by default, but we need to do it before we ship it. --jst | ** Talked to dveditz about how to do the security review for the HTML5 parser, and it's not clear what the best format for the review would be. But we did decide that it's not something we need to do before turning the parser on by default, but we need to do it before we ship it. --jst |
Revision as of 13:22, 25 May 2010
This page outlines what needs to be done to ship a release with the HTML5 parser enabled by default.
Things that need to be done before shipping the HTML5 parser in a final Firefox release
- Fix "[HTML5]" bugs marked P2. (hsivonen)
- 561874 The HTML5 parser needs limit DOM tree depth
- Patch exists; needs testing.
- Bugs waiting on Hixie or W3C WGs
- 561874 The HTML5 parser needs limit DOM tree depth
- Reviews on patches
- Security review.
- Talked to dveditz about how to do the security review for the HTML5 parser, and it's not clear what the best format for the review would be. But we did decide that it's not something we need to do before turning the parser on by default, but we need to do it before we ship it. --jst
- 544994Create a "slow tp" test suite for exercising speculative parsing. (bnewman)
- What if this suite reveals something bad?
Suspended items that may re-enter the list of release blockers
- Suspended bugs that were previously P2
- 482917 Make HTML5 parsing not regress stream data availability to extensions
- There's now a patch but no way to test it.
- Suspended, because there are no known extensions that use the API in question and are compatible with Firefox 3.6.
- Time estimate: Unknown. (Need to find an extension that actually uses this. The alternative is writing an extension just for testing.)
- 482917 Make HTML5 parsing not regress stream data availability to extensions
Notable evangelism bugs
- Bugs that need site-side fixes
- 540480 Hootsuite.com dashboard not loading with HTML5 parser turned on
- Site contacted, contact acknowledged (hsivonen)
- 553795 Blank page on weer.nl (Windows only)
- No owner
- Bad browser sniffing leads to document.write without an insertion point
- 565689 </script> in string literal breaks out of script early on wsecu.org
- Site contacted (mbrubeck)
- Bank
- 565938 Blank page on LinkedIn Recruiter
- Site rep CCed on the bug.
- Bad browser sniffing leads to document.write without an insertion point
- 540480 Hootsuite.com dashboard not loading with HTML5 parser turned on