254
edits
Platform/HTML5 parser tasks: Difference between revisions
Move the slop tp test suite, since it is no longer considered to be a prerequisite for turning the parser on
(→Things that need to be done before shipping the HTML5 parser in a final Firefox release: Mark stream availability to extensions as a suspended item) |
(Move the slop tp test suite, since it is no longer considered to be a prerequisite for turning the parser on) |
||
| Line 13: | Line 13: | ||
***Waiting for review comments getting addressed and super-review. | ***Waiting for review comments getting addressed and super-review. | ||
*Review the unreviewed parser core code. (sicking) | *Review the unreviewed parser core code. (sicking) | ||
*Reviews on existing patches | *Reviews on existing patches | ||
**[https://bugzilla.mozilla.org/show_bug.cgi?id=551344 551344] Patches addressing sicking's review comments (sicking) | **[https://bugzilla.mozilla.org/show_bug.cgi?id=551344 551344] Patches addressing sicking's review comments (sicking) | ||
| Line 40: | Line 39: | ||
*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 | ||
*Create 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 items that may re-enter the list of release blockers== | ||