Platform/HTML5 parser tasks: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 4: Line 4:


* Fix "[HTML5]" bugs marked [https://bugzilla.mozilla.org/buglist.cgi?priority=P2;short_desc=%5bHTML5%5d;field0-0-0=short_desc;query_format=advanced;bug_status=NEW;bug_status=ASSIGNED;short_desc_type=allwordssubstr;type0-0-0=notsubstring;value0-0-0=%5bPatch%5d P2]. (hsivonen)
* Fix "[HTML5]" bugs marked [https://bugzilla.mozilla.org/buglist.cgi?priority=P2;short_desc=%5bHTML5%5d;field0-0-0=short_desc;query_format=advanced;bug_status=NEW;bug_status=ASSIGNED;short_desc_type=allwordssubstr;type0-0-0=notsubstring;value0-0-0=%5bPatch%5d P2]. (hsivonen)
** [https://bugzilla.mozilla.org/show_bug.cgi?id=552938 552938] Implement the SVG load event in text/html
***Patch exists. Regresses [https://bugzilla.mozilla.org/show_bug.cgi?id=535691 bug 535691]. Don't know why, yet.
**Bugs waiting on Hixie or W3C WGs
**Bugs waiting on Hixie or W3C WGs
*** [https://bugzilla.mozilla.org/show_bug.cgi?id=563526 563526] Early U+0000 eats frameset (Can't configure D-Link DSL-G604T ADSL router)
*** [https://bugzilla.mozilla.org/show_bug.cgi?id=563526 563526] Early U+0000 eats frameset (Can't configure D-Link DSL-G604T ADSL router)
Line 15: Line 13:
** [https://bugzilla.mozilla.org/show_bug.cgi?id=566280 566280] Plain text prefixed by U+0000 displays only U+FFFD (sicking)
** [https://bugzilla.mozilla.org/show_bug.cgi?id=566280 566280] Plain text prefixed by U+0000 displays only U+FFFD (sicking)
** [https://bugzilla.mozilla.org/show_bug.cgi?id=568800 568800] Implement spec changes to named character reference parsing in attribute values (sicking)
** [https://bugzilla.mozilla.org/show_bug.cgi?id=568800 568800] Implement spec changes to named character reference parsing in attribute values (sicking)
*Patches waiting landing (due to CLOSED TREE)
** [https://bugzilla.mozilla.org/show_bug.cgi?id=552938 552938] Implement the SVG load event in text/html
*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 12:25, 7 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)
    • Bugs waiting on Hixie or W3C WGs
      • 563526 Early U+0000 eats frameset (Can't configure D-Link DSL-G604T ADSL router)
      • 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.
  • Reviews on patches
    • 566280 Plain text prefixed by U+0000 displays only U+FFFD (sicking)
    • 568800 Implement spec changes to named character reference parsing in attribute values (sicking)
  • Patches waiting landing (due to CLOSED TREE)
    • 552938 Implement the SVG load event in text/html
  • 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
    • 570309 Breakage on CNN Money.
      • No owner.
      • Breakage caused by a tradeoff where the other options have downsides, too.