Love your work Adam, Eric and all involved with this project.<div><br><br><div class="gmail_quote">On 22 July 2010 11:30, Adam Barth <span dir="ltr"><<a href="mailto:abarth@webkit.org">abarth@webkit.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">We're getting close to enabling the HTML5 tree builder on trunk. Once<br>
we do that, we'll have the core of the HTML5 parsing algorithm turned<br>
on, including SVG-in-HTML. There are still a bunch of details left to<br>
finish (such as fragment parsing, MathML entities, and better error<br>
reporting), but this marks a significant milestone for this work.<br>
<br>
The tree builder is markedly more complicated than the tokenizer, and<br>
I'm sure we're going to have some bad regressions. I'd like to ask<br>
your patience and your help to spot and triage these regressions.<br>
We've gotten about as much mileage as we can out of the HTML5lib test<br>
suite and the LayoutTests. The next step for is to see how the<br>
algorithm works in the real world.<br>
<br>
There are about 84 tests that will require new expectations, mostly<br>
due to invisible differences in render tree dumps (e.g., one more or<br>
fewer 0x0 render text). In about half the cases, we've manually<br>
verified that our new results agree with the Firefox nightly builds,<br>
which is great from a compliance and interoperability point of view.<br>
The other half involve things like the exact text for the <isindex>,<br>
which we've chosen to match the spec exactly, or the <keygen> element,<br>
which needs some shadow DOM love to hide its implementation details<br>
from web content.<br>
<br>
As for performance, last time we ran our parser benchmark, the new<br>
tree builder was 1% faster than the old tree builder. There's still a<br>
bunch of low-hanging performance work we can do, such as atomizing<br>
strings and inlining functions. If you're interested in performance,<br>
let me or Eric know and we can point you in the right direction.<br>
<br>
I don't have an exact timeline for when we're going to throw the<br>
switch, but sometime in the next few days. If you'd like us to hold<br>
off for any reason, please let Eric or me know.<br>
<br>
Adam<br>
<br>
P.S., you can follow along by CCing yourself on the master bug,<br>
<<a href="https://bugs.webkit.org/show_bug.cgi?id=41123" target="_blank">https://bugs.webkit.org/show_bug.cgi?id=41123</a>>, or by looking at our<br>
LayoutTest failure triage spreadsheet,<br>
<<a href="https://spreadsheets.google.com/ccc?key=0AlC4tS7Ao1fIdEo0SFdLaVpiclBHMVNQcHlTenV5TEE&hl=en" target="_blank">https://spreadsheets.google.com/ccc?key=0AlC4tS7Ao1fIdEo0SFdLaVpiclBHMVNQcHlTenV5TEE&hl=en</a>>.<br>
_______________________________________________<br>
webkit-dev mailing list<br>
<a href="mailto:webkit-dev@lists.webkit.org">webkit-dev@lists.webkit.org</a><br>
<a href="http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev" target="_blank">http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev</a><br>
</blockquote></div><br></div>