- From: liorean <liorean@gmail.com>
- Date: Mon, 28 Jan 2008 16:30:58 +0100
- To: "HTML WG" <public-html@w3.org>
> Simon Pieters skrev: > > Consider that you make a site for a client, in XHTML, but served as > > text/html to IE. You use a popular CMS so that the client can update the > > site himself. The site validates and all is nice and dandy, a work well > > done. > > > > Now 6 months later the client updates the front page on his site and > > forgets to escape an ampersand. The client doesn't notice because he > > uses IE. Suddenly the client is locking out customers without knowing > > about it. On 28/01/2008, temp17@staldal.nu <temp17@staldal.nu> wrote: > This implies that there is a browser in use which > > a) Refuse to display illformed XHTML when served as text/html Not at all. The document was specifically served as text/html to ie, implying that other browsers got application/xhtml+xml. > AND > b) Correctly display HTML with incorrect character entities > Which browser is that? Tell me which browser doesn't support unescaped ampersands in HREF and SRC attributes for text/html content? It's one of the most common XHTML coding errors around. It gets ignored in HTML mode, but YSoD in XML mode. -- David "liorean" Andersson
Received on Monday, 28 January 2008 15:31:21 UTC