Platform/HTML5 parser tasks: Difference between revisions

Jump to navigation Jump to search
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
***Patch exists. Regresses [https://bugzilla.mozilla.org/show_bug.cgi?id=535691 bug 535691]. Don't know why, yet.
**Bugs waiting on Hixie or W3C WGs
**Bugs waiting on Hixie or W3C WGs
*** [https://bugzilla.mozilla.org/show_bug.cgi?id=563526 563526] Early U+0000 eats frameset (Can't configure D-Link DSL-G604T ADSL router)
*** [https://bugzilla.mozilla.org/show_bug.cgi?id=563526 563526] Early U+0000 eats frameset (Can't configure D-Link DSL-G604T ADSL router)
Line 15: Line 13:
** [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)
** [https://bugzilla.mozilla.org/show_bug.cgi?id=568800 568800] Implement spec changes to named character reference parsing in attribute values (sicking)
*Patches waiting landing (due to CLOSED TREE)
** [https://bugzilla.mozilla.org/show_bug.cgi?id=552938 552938] Implement the SVG load event in text/html
*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
254

edits

Navigation menu