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: Add a bug
(Add recently filed P2 bugs) |
|||
| Line 41: | Line 41: | ||
** [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 | ||
***''Time estimate'': Less than a day if hacked around in the parser. Unknown if fixed more properly in layout. | ***''Time estimate'': Less than a day if hacked around in the parser. Unknown if fixed more properly in layout. | ||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=558302 558302] <button> should not be scoping | |||
***''Time estimate'': Trivial (flipping one boolean), but waiting for a spec change first. | |||
*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 | ||