- From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- Date: Tue, 23 Mar 2010 20:25:40 +0100
- To: Krzysztof Maczyński <1981km@gmail.com>
- Cc: www-validator@w3.org
Leif Halvard Silli, Tue, 23 Mar 2010 19:56:17 +0100: > Krzysztof Maczyński, Mon, 22 Mar 2010 23:38:56 +0100: >> Thanks, Leif, for sharing your ideas ([1], [2])! They're definitely >> interesting and occasionally useful. >> >> I've got one more question. Can the parser-hack PI be hidden somehow >> from a compliant XML parser? > > Does it need to be hidden from a compliant XML parser? Assuming Firefox > and and Opera are compliant, then there were no problems there, that I > could see, when I tested the hack on page served as > application/xhtml+xml. Webkit had a problem - apparently a bug, related > to how it treats <?pi ?>s - it seemed to treat them as SGML PIs rather > than as XML PIs. I filed a bug in the Webkt project for this. Which XML > parser are you dealing with? About Webkit's XML PI bug: It only materializes inside the DOCTYPE. That is: it does not materialize when the PI is the child of <html> or another HTML element, as you can read in my bug report: https://bugs.webkit.org/show_bug.cgi?id=35954 Interestingly, Webkit's elder brother - Konqueror - does not have this bug. >> [1] http://lists.w3.org/Archives/Public/public-html/2010Feb/0627.html Note that [1] was a HTML4 *only* hack. >> [2] http://lists.w3.org/Archives/Public/www-validator/2010Mar/0027.html -- leif halvard silli
Received on Tuesday, 23 March 2010 19:26:15 UTC