RESOLVED FIXED 39259
MASTER: WebKit needs an HTML5 Tokenizer 
https://bugs.webkit.org/show_bug.cgi?id=39259
Summary MASTER: WebKit needs an HTML5 Tokenizer
Eric Seidel (no email)
Reported 2010-05-17 19:57:07 PDT
MASTER: WebKit needs an HTML5 Tokenizer Adam and I are going to work on adding one this week. This is a master bug which we will relate all of the various bugs to. We're going to start by forking from PreloadScanner. We will be in #webkit and happy to discuss our design thoughts.
Attachments
Add attachment proposed patch, testcase, etc.
Adam Barth
Comment 1 2010-05-20 09:51:54 PDT
Henri mentioned that Mozilla has 6 open evangelism related to their HTML5 parser: http://www.w3.org/Bugs/Public/show_bug.cgi?id=9767#c3
Adam Barth
Comment 2 2010-06-04 21:03:27 PDT
Here's the spreadsheet we're using to triage the remaining LayoutTest failures: https://spreadsheets.google.com/ccc?key=0AppchfQ5mBrEdDFJUW5DOGNsdmtvZkN0ZmIzMjdaT0E&hl=en Currently, there are around 150 failures. However, for some of them, our new behavior is correct w.r.t. the spec but the tests have their expectations set to the old parser behavior.
Adam Barth
Comment 3 2010-06-16 02:23:43 PDT
This is now enabled by default. There are still some dependent bugs to finish up, but we can close the master. We'll probably open a new master to deal with regressions.
Adam Barth
Comment 4 2010-06-23 17:48:16 PDT
Here's the master bug for tracking compatibility regressions due to the new tokenizer: https://bugs.webkit.org/show_bug.cgi?id=41115
Eric Seidel (no email)
Comment 5 2011-05-17 10:54:12 PDT
*** Bug 40634 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.