Subject: Re: [xsl] Understanding why <tag></tag> is the way it is (was Re: [xsl] IE Client side transformation issue) From: David Carlisle <davidc@xxxxxxxxx> Date: Fri, 3 Aug 2007 17:03:36 +0100 |
> If you send it with an html mime type, then what you _should_ > get is the same as if the input had been >abc with a visible > sign, which is why incidentally the so called "compatibility rules" in XHTML are fundamentally broken. Relying on <br /> to produce a linebreak not a linebreak followed by a > sign means that you are _relying_ on the browsers using a non conformant parser for HTML. Browsers almost always do use a non conformant parse so it sort of works, but a "standard" should never have suggested that it is a good thing. HTML validating systems often do use an SGML parser (nsgmls, typically) and there things often break, <br /> validates as the extra text > is allowed in any content model that allows <br/> but for example <meta .../> fails to validate as it is equivalent to <meta ...>> and you cant have extra > text in the head of the document. David ________________________________________________________________________ The Numerical Algorithms Group Ltd is a company registered in England and Wales with company number 1249803. The registered office is: Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom. This e-mail has been scanned for all viruses by Star. The service is powered by MessageLabs. ________________________________________________________________________
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Understanding why <tag></, David Carlisle | Thread | Re: [xsl] Understanding why <tag></, Norman Gray |
Re: [xsl] Understanding why <tag></, David Carlisle | Date | Re: [xsl] IE Client side transforma, David Carlisle |
Month |