Platform/HTML5 parser tasks

This page outlines what needs to happen to 1) enable the HTML5 parser by default on mozilla-central and 2) ship a release with the HTML5 parser enabled by default.

The HTML5 parser has been suitable for dogfooding for over a year and in the past couple of months there have been virtually no new site compat bugs. Thus, the parser is already alpha quality from a user POV but not from a zero test suite regressions POV.

Things that need to happen before turning the HTML5 parser on by default

• Land 13 or so reviewed patches in hsivonen's queue (trivial once the tree is green). (hsivonen)
• Get reviews on pending patches. (various people)
• Make tp4 not regress. (hsivonen)
• Drive testsuite failures to zero. (hsivonen but help would be useful)
• Either change form submission code to deal with IE-style isindex (hsivonen but help would be useful) or change the parser to use a Gecko-style isindex for now (hsivonen).
• Update the html5lib test suite snapshot used by mochitest. (jgriffin)
• Review the unreviewed parser core code. (sicking?)
  • Some more code documentation on the Java side would be useful. (hsivonen)
• Create a "slow tp" test suite for exercising speculative parsing. (bnewman) What if this suite reveals something bad?

Things that need to happen before shipping the HTML5 parser is a final Firefox release

• Fix "[HTML5]" bugs marked P2. (hsivonen)