Platform/HTML5 parser tasks: Difference between revisions

Jump to navigation Jump to search
Line 7: Line 7:
*** Need to fix random orange.
*** Need to fix random orange.
**Bugs waiting on Hixie or W3C WGs
**Bugs waiting on Hixie or W3C WGs
*** [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
****Preliminary layout patch exists. Waiting for the CSS WG to approve the solution or propose another solution.
*** [https://bugzilla.mozilla.org/show_bug.cgi?id=560256 560256] Old document gets blown away when dynamically added script does document.write.
*** [https://bugzilla.mozilla.org/show_bug.cgi?id=560256 560256] Old document gets blown away when dynamically added script does document.write.
**** Ignoring document.write from network task sources when the insertion point is undefined would mitigate 4 out of the 6 current HTML5 parser evang bugs. [http://www.w3.org/Bugs/Public/show_bug.cgi?id=9767 Spec bug filed].
**** Ignoring document.write from network task sources when the insertion point is undefined would mitigate 4 out of the 6 current HTML5 parser evang bugs. [http://www.w3.org/Bugs/Public/show_bug.cgi?id=9767 Spec bug filed].
Line 20: Line 18:
** [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)
** [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 (bzbarsky)
*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
254

edits

Navigation menu