254
edits
Platform/HTML5 parser tasks: Difference between revisions
Jump to navigation
Jump to search
→Things that need to be done before shipping the HTML5 parser in a final Firefox release
| Line 13: | Line 13: | ||
** [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) | ||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=575175 575175] Deal with Unicode decoder consuming -1 bytes (smontagu) | ** [https://bugzilla.mozilla.org/show_bug.cgi?id=575175 575175] Deal with Unicode decoder consuming -1 bytes (smontagu) | ||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=577508] Hide old document when new one pops a dialog (bz) | ** [https://bugzilla.mozilla.org/show_bug.cgi?id=577508 577508] Hide old document when new one pops a dialog (bz) | ||
*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 | ||