Platform/HTML5 parser tasks: Difference between revisions

(→‎Notable evangelism bugs: Progress on hootsuite)
Line 10: Line 10:
*** [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  
****Waiting for Hixie to resolve bugs discovered in the spec text while implementing this.
****Waiting for Hixie to resolve bugs discovered in the spec text while implementing this.
*** [https://bugzilla.mozilla.org/show_bug.cgi?id=552938 552938] Implement the SVG load event in text/html
****''Time estimate'': Less than a day, but waiting for the SVG WG to decide whether to remove this event instead.
*** [https://bugzilla.mozilla.org/show_bug.cgi?id=557197 557197] &amp;#13; 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] &amp;#13; 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.
****Preliminary layout patch exists. Waiting for the CSS WG to approve the solution or propose another solution.
*Reviews on patches
*Reviews on patches
** [https://bugzilla.mozilla.org/show_bug.cgi?id=565432 565432] Higher layers are now responsible for ignoring space characters before URL in href (bzbarsky)
*** [https://bugzilla.mozilla.org/show_bug.cgi?id=552938 552938] Implement the SVG load event in text/html (jwatt)
*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