254
edits
Platform/HTML5 parser tasks: Difference between revisions
→Things that need to be done before shipping the HTML5 parser in a final Firefox release: Move a bug to the review list
(→Things that need to be done before shipping the HTML5 parser in a final Firefox release: Create a list of pending P2 reviews) |
(→Things that need to be done before shipping the HTML5 parser in a final Firefox release: Move a bug to the review list) |
||
| Line 34: | Line 34: | ||
***''Time estimate'': Less than a day, provided that reviewers accept slightly ugly code. (A non-ugly solution would seem to require a dramatic refactoring.) | ***''Time estimate'': Less than a day, provided that reviewers accept slightly ugly code. (A non-ugly solution would seem to require a dramatic refactoring.) | ||
** [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 | ||
***''Time estimate'': Less than a day. | ***''Time estimate'': Less than a day. | ||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=557197 557197] in element content expands to CR and shows up as a non-collapsing space in layout | ** [https://bugzilla.mozilla.org/show_bug.cgi?id=557197 557197] in element content expands to CR and shows up as a non-collapsing space in layout | ||
| Line 43: | Line 41: | ||
*Reviews on existing patches | *Reviews on existing patches | ||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=548232 548232] Make meta charset have no effect on document.open()ed documents. (bzbarsky) | ** [https://bugzilla.mozilla.org/show_bug.cgi?id=548232 548232] Make meta charset have no effect on document.open()ed documents. (bzbarsky) | ||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=555906 555906] </datalist> doesn't implicitly close an <option> (bnewman) | |||
*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 | ||