- From: <bugzilla@jessica.w3.org>
- Date: Thu, 10 Feb 2011 23:52:46 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12031 Eric Seidel <eric@webkit.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |eric@webkit.org, | |w3c@adambarth.com --- Comment #1 from Eric Seidel <eric@webkit.org> 2011-02-10 23:52:45 UTC --- WebKit has implemented fragment parsing for HTML5, supporting parsing both with and without a contextElement per the spec. However, every case which we initially did not use a context element was *wrong*. https://bugs.webkit.org/show_bug.cgi?id=44450 is one such example of where we initially didn't use a contextElement, and later had to add a fake <body> context element to make parsing correct. We have recently moved away from using a real dummy document for the fragment parsing. And in doing so broken the ability to parse fragments w/o a context element 100% correctly. Since there is currently no way in WebKit (or in the spec as far as I can tell?) to trigger parsing a fragment w/o a context element, this is OK. Since there is no way in WebKit (or the spec) is seems that the spec should either provide an example of parsing w/o a context element (when such would be used) or note that that case is impossible to provide implementors (like webkit) more freedom of implementation (by assuming that there will always be a context element, as is currently the case). -- 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 Thursday, 10 February 2011 23:52:48 UTC