Platform/HTML5 parser tasks: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(6 intermediate revisions by the same user not shown)
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
** [https://bugzilla.mozilla.org/show_bug.cgi?id=569528 569528] <h5> inside <button> inside <p> implicitly closes the <p>
*** Need to fix random orange.
** [https://bugzilla.mozilla.org/show_bug.cgi?id=579846 579846] HTML5 parser regresses cache-control support in meta pragmas
**Bugs waiting on Hixie or W3C WGs
** [https://bugzilla.mozilla.org/show_bug.cgi?id=579867 579867] Implement July 2010 spec changes to SVG in HTML
*** [https://bugzilla.mozilla.org/show_bug.cgi?id=569528 569528] <h5> inside <button> inside <p> implicitly closes the <p>
*** Related [https://bugzilla.mozilla.org/show_bug.cgi?id=577416 577416] [https://bugzilla.mozilla.org/show_bug.cgi?id=574884 574884] [https://bugzilla.mozilla.org/show_bug.cgi?id=577418 577418]
** [https://bugzilla.mozilla.org/show_bug.cgi?id=564098 564098] "ASSERTION: Script global object not ready"
** [https://bugzilla.mozilla.org/show_bug.cgi?id=577508 577508] Hide old document when new one pops a dialog
*Reviews on patches
*Reviews on patches
** [https://bugzilla.mozilla.org/show_bug.cgi?id=563526 563526] Early U+0000 eats frameset (Can't configure D-Link DSL-G604T ADSL router) (sicking)
** [https://bugzilla.mozilla.org/show_bug.cgi?id=574884 574884] <math></html> crashes (sicking)
****Patch that anticipates a spec change exists.
** [https://bugzilla.mozilla.org/show_bug.cgi?id=568470 568470] A page with a sleep() in the script generating it shows no data until after the sleep ends (bnewman)
** [https://bugzilla.mozilla.org/show_bug.cgi?id=560256 560256] Old document gets blown away when dynamically added script does document.write. (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=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)
** [https://bugzilla.mozilla.org/show_bug.cgi?id=575175 575175] Deal with Unicode decoder consuming -1 bytes (smontagu)
*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
* [https://bugzilla.mozilla.org/show_bug.cgi?id=544994 544994]Create a "slow tp" test suite for exercising speculative parsing. (bnewman)
* [https://bugzilla.mozilla.org/show_bug.cgi?id=544994 544994]Create a "slow tp" test suite for exercising speculative parsing. (who owns this now?)
** ''What if this suite reveals something bad?''
** ''What if this suite reveals something bad?''


Latest revision as of 15:44, 19 July 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)
    • 569528 <h5> inside <button> inside <p> implicitly closes the <p>
    • 579846 HTML5 parser regresses cache-control support in meta pragmas
    • 579867 Implement July 2010 spec changes to SVG in HTML
    • 564098 "ASSERTION: Script global object not ready"
    • 577508 Hide old document when new one pops a dialog
  • Reviews on patches
    • 574884 <math></html> crashes (sicking)
    • 570309 -- > closing comments breaks CNN Money (sicking)
    • 575175 Deal with Unicode decoder consuming -1 bytes (smontagu)
  • 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. (who owns this now?)
    • 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
Retrieved from "https://wiki.mozilla.org/index.php?title=Platform/HTML5_parser_tasks&oldid=239130"