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 doc.write spec bug
(→Things that need to be done before shipping the HTML5 parser in a final Firefox release: Add doc.write spec bug) |
|||
| Line 10: | Line 10: | ||
*** [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 | ||
****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. | ||
*** [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]. | |||
*Reviews on patches | *Reviews on patches | ||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=552938 552938] Implement the SVG load event in text/html (jwatt) | ** [https://bugzilla.mozilla.org/show_bug.cgi?id=552938 552938] Implement the SVG load event in text/html (jwatt) | ||