- From: <bugzilla@jessica.w3.org>
- Date: Thu, 06 Sep 2012 17:17:50 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15180 --- Comment #10 from Robin Berjon <robin@w3.org> 2012-09-06 17:17:49 UTC --- (In reply to comment #9) > Robin, how is your proposed solution compatible with incremental parsing? As far as I could work out, here's what happens. If the document is clearly XML, and the root element isn't "html", then if it matches something for an external handler like Atom, it might be dispatched off to that. If however it doesn't match that the browser seems to just parse, parse, parse and render nothing. If at some point it suddenly sees an HTML/SVG/MathML element, it will render accordingly (applying the default UA style sheet and all). If it reaches the end without having seen one such element, then it shows the tree view. I tried this out by feeding browsers some megabytes-long document. I'm not sure how that could hurt incremental parsing, though I'd be happy to learn. It certainly hurts incremental rendering (of XML documents that have no HTML content) but this doesn't not strike me as a huge problem. -- Configure bugmail: https://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, 6 September 2012 17:17:54 UTC