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: Landed the carriage return patch
(→Things that need to be done before shipping the HTML5 parser in a final Firefox release: Landed the carriage return patch) |
|||
| Line 15: | Line 15: | ||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=571389 571389] <basefont> breaks out of <head> (sicking) | ** [https://bugzilla.mozilla.org/show_bug.cgi?id=571389 571389] <basefont> breaks out of <head> (sicking) | ||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=570309 570309] -- > closing comments breaks CNN Money (sicking) | ** [https://bugzilla.mozilla.org/show_bug.cgi?id=570309 570309] -- > closing comments breaks CNN Money (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 | ||