254
edits
(→Things that need to be done before shipping the HTML5 parser in a final Firefox release: Move bug to review list) |
|||
| Line 4: | Line 4: | ||
* Fix "[HTML5]" bugs marked [https://bugzilla.mozilla.org/buglist.cgi?priority=P2;short_desc=%5bHTML5%5d;field0-0-0=short_desc;query_format=advanced;bug_status=NEW;bug_status=ASSIGNED;short_desc_type=allwordssubstr;type0-0-0=notsubstring;value0-0-0=%5bPatch%5d P2]. (hsivonen) | * Fix "[HTML5]" bugs marked [https://bugzilla.mozilla.org/buglist.cgi?priority=P2;short_desc=%5bHTML5%5d;field0-0-0=short_desc;query_format=advanced;bug_status=NEW;bug_status=ASSIGNED;short_desc_type=allwordssubstr;type0-0-0=notsubstring;value0-0-0=%5bPatch%5d P2]. (hsivonen) | ||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=552938 552938] Implement the SVG load event in text/html | ** [https://bugzilla.mozilla.org/show_bug.cgi?id=552938 552938] Implement the SVG load event in text/html | ||
***Patch exists. Need to investigate an unexpected increased assertion count on one test. Don't know how much work that's going to take. | ***Patch exists. Need to investigate an unexpected increased assertion count on one test. Don't know how much work that's going to take. | ||
| Line 16: | Line 15: | ||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=561874 561874] The HTML5 parser needs limit DOM tree depth (bzbarsky) | ** [https://bugzilla.mozilla.org/show_bug.cgi?id=561874 561874] The HTML5 parser needs limit DOM tree depth (bzbarsky) | ||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=566280 566280] Plain text prefixed by U+0000 displays only U+FFFD (sicking) | ** [https://bugzilla.mozilla.org/show_bug.cgi?id=566280 566280] Plain text prefixed by U+0000 displays only U+FFFD (sicking) | ||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=568800 568800] Implement spec changes to named character reference parsing in attribute values (sicking) | |||
*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 | ||
edits