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 README to review list
(→Things that need to be done before shipping the HTML5 parser in a final Firefox release: move README to review list) |
|||
| Line 25: | Line 25: | ||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=537948 537948] The procedure to fix a <a> around a <tr> element is acting weird. | ** [https://bugzilla.mozilla.org/show_bug.cgi?id=537948 537948] The procedure to fix a <a> around a <tr> element is acting weird. | ||
***''Time estimate'': Less than a day to discover if this is a parser bug or a spec bug. If this is a spec bug, the time it takes to get a spec fix is unknown. | ***''Time estimate'': Less than a day to discover if this is a parser bug or a spec bug. If this is a spec bug, the time it takes to get a spec fix is unknown. | ||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=552908 552908] Implement spec changes to SVG </a> and </font> handling | ** [https://bugzilla.mozilla.org/show_bug.cgi?id=552908 552908] Implement spec changes to SVG </a> and </font> handling | ||
***''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.) | ||
| Line 35: | Line 33: | ||
*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=539210 539210] Revise the translator README to cover all makefile functionality. (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 | ||