- From: <bugzilla@jessica.w3.org>
- Date: Fri, 10 Sep 2010 18:28:23 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9659 --- Comment #9 from Eric Seidel <eric@webkit.org> 2010-09-10 18:28:19 --- WebKit also tries hard to keep the individual pieces of the spec as isolated leaf node classes. Tokenizer *cannot* talk to the TreeBuilder in WebKit's implementation. The places in the spec which require such, have the TreeBuilder setting some state on the Tokenizer instead. The tokenizer is called by the "DocumentParser" which drives the whole process. The DocumentParser passes source to an InputStreamPreprocessor which readies the source for the Tokenizer. The Tokenizer returns tokens back to the DocumentParser. The DocumentParser passes those to the TreeBuilder. The TreeBuilder yields when necessary to allow the DocumentParser to run the ScriptRunner on its behalf, etc. Note that each class is separate from each other, and generally never calls the others directly. My point of all this is just to discourage further spec modifications which tightly couple these parts. Keeping them loosly coupled (and keeping communication unidirectional, from the TreeBuilder to the Tokenizer) makes implementation a whole lot simpler and cleaner. :) -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Friday, 10 September 2010 18:28:24 UTC