Platform/HTML5 parser tasks: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 6: Line 6:
** [https://bugzilla.mozilla.org/show_bug.cgi?id=552938 552938] Implement the SVG load event in text/html
** [https://bugzilla.mozilla.org/show_bug.cgi?id=552938 552938] Implement the SVG load event in text/html
*** Need to fix random orange.
*** Need to fix random orange.
** [https://bugzilla.mozilla.org/show_bug.cgi?id=570309 570309] -- > closing comments breaks CNN Money
*** Simple to fix in code, but the fix may break more sites. Gotta try and feed the findings back to the spec.
**Bugs waiting on Hixie or W3C WGs
**Bugs waiting on Hixie or W3C WGs
*** [https://bugzilla.mozilla.org/show_bug.cgi?id=569528 569528] button should be scoping for the purpose of start tags implicitly closing paragraphs
*** [https://bugzilla.mozilla.org/show_bug.cgi?id=569528 569528] button should be scoping for the purpose of start tags implicitly closing paragraphs
Line 16: Line 14:
*** [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].
**** Patch exists, need to adjusts tests to match.
*** [https://bugzilla.mozilla.org/show_bug.cgi?id=569528 569528] <h5> inside <button> inside <p> implicitly closes the <p>
*** [https://bugzilla.mozilla.org/show_bug.cgi?id=569528 569528] <h5> inside <button> inside <p> implicitly closes the <p>
*Reviews on patches
*Reviews on patches
Line 22: Line 21:
** [https://bugzilla.mozilla.org/show_bug.cgi?id=570898 570898] Isindex prompt initialized too early (sicking)
** [https://bugzilla.mozilla.org/show_bug.cgi?id=570898 570898] Isindex prompt initialized too early (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=571389 571389] <basefont> breaks out of <head> (sicking)
** [https://bugzilla.mozilla.org/show_bug.cgi?id=570309 570309] -- > closing comments breaks CNN Money (sicking)
*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

Revision as of 15:05, 18 June 2010

This page outlines what needs to be done to ship a release with the HTML5 parser enabled by default.

Things that need to be done before shipping the HTML5 parser in a final Firefox release

  • Fix "[HTML5]" bugs marked P2. (hsivonen)
    • 552938 Implement the SVG load event in text/html
      • Need to fix random orange.
    • Bugs waiting on Hixie or W3C WGs
      • 569528 button should be scoping for the purpose of start tags implicitly closing paragraphs
      • 563526 Early U+0000 eats frameset (Can't configure D-Link DSL-G604T ADSL router)
        • Patch that anticipates a spec change exists.
      • 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.
      • 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. Spec bug filed.
        • Patch exists, need to adjusts tests to match.
      • 569528 <h5> inside <button> inside <p> implicitly closes the <p>
  • Reviews on patches
    • 566879 innerHTML-inserted form controls participate in form state restoration (regressing from making innerHTML parse directly into the context node) (smaug)
    • 568470 A page with a sleep() in the script generating it shows no data until after the sleep ends (bnewman)
    • 570898 Isindex prompt initialized too early (sicking)
    • 571389 <basefont> breaks out of <head> (sicking)
    • 570309 -- > closing comments breaks CNN Money (sicking)
  • 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
  • 544994Create a "slow tp" test suite for exercising speculative parsing. (bnewman)
    • What if this suite reveals something bad?

Suspended items that may re-enter the list of release blockers

  • Suspended bugs that were previously P2
    • 482917 Make HTML5 parsing not regress stream data availability to extensions
      • There's now a patch but no way to test it.
      • Suspended, because there are no known extensions that use the API in question and are compatible with Firefox 3.6.
      • Time estimate: Unknown. (Need to find an extension that actually uses this. The alternative is writing an extension just for testing.)

Notable evangelism bugs

  • Bugs that need site-side fixes
    • 540480 Hootsuite.com dashboard not loading with HTML5 parser turned on
      • Site contacted, contact acknowledged (hsivonen)
    • 553795 Blank page on weer.nl (Windows only)
      • No owner
      • Bad browser sniffing leads to document.write without an insertion point
    • 565689 </script> in string literal breaks out of script early on wsecu.org
      • Site contacted (mbrubeck)
      • Bank
    • 565938 Blank page on LinkedIn Recruiter
      • Site rep CCed on the bug.
      • Bad browser sniffing leads to document.write without an insertion point