Platform/HTML5 parser tasks

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
  - Patch exists. Regresses bug 535691. Don't know why, yet.
- 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)
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 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.)