Yep, this was mainlined in Firefox 4 (with Gecko 2.0).
> I think IE has made a bunch of noise about it too
Support is being built, it's planned for IE10.
> I don't follow WebKit all that closely, but I'd be surprised if they haven't moved towards an HTML5 parser
The HTML5 parsing algorithm has been in Webkit since the second half of 2010.
And you have not asked, but HTML5 parsing was officially released in Opera 11.6 last month.
I hope that's not related to the annoying freezes the community's been complaining about since that release...
From an interoperability point of view the HTML parsing algorithm is the poster child for the success of the HTML effort; there is a testsuite of several thousand tests [1] (also submitted to the W3C [2]) that has contributions from multiple browser vendors and a number of unaffiliated individuals. Although parsing isn't sexy in the way that, say, <canvas> is, getting interoperable parsing makes it much easier to create cross-browser content (at Opera we closed a huge number of site-compatibilty bugs when we landed the new algorithm).
There are also a few open-source implementations that are not tied to browsers e.g. for python (and kind of also PHP) [3], for java [4] (fun fact: the gecko C++ implementation is generated from that java implementation) and javascript [5] https://github.com/andreasgal/dom.js It would be great to see more conforming implementations for other languages, or to see libraries like libxml2 that have existing ad-hoc HTML parsers update their implementations to match the spec.
[1] http://code.google.com/p/html5lib/source/browse/#hg%2Ftestda...
[2] http://w3c-test.org/html/tests/submission/Opera/html5lib/
[3] http://code.google.com/p/html5lib/
These days, however, we have the HTML5 parsing algorithm, reverse-engineered from various vendors' web browsers but actually documented and implementable (still horribly complicated, but that's legacy content for you). Not only is the HTML5 parsing algorithm designed to be compatible with legacy browsers, modern browsers are replacing their old parsing code with new HTML5-compatible implementations, so parsing should be even more consistent (I know Firefox has switched to an HTML5 parser, I think IE has made a bunch of noise about it too; I don't follow WebKit all that closely, but I'd be surprised if they haven't moved towards an HTML5 parser).