W3C home > Mailing lists > Public > whatwg@whatwg.org > May 2007

[whatwg] Style sheet loading and parsing (over HTTP)

From: Kristof Zelechovski <giecrilj@stegny.2a.pl>
Date: Thu, 31 May 2007 12:20:07 +0200
Message-ID: <000f01c7a36d$43268870$1a01080a@POCZTOWIEC>
You should rather begin with (plain text) CR LF to subvert document type
sniffing.  It is meant to be plain text, after all.  You do not use tags in
plain text, be they fake or genuine.

-----Original Message-----
From: whatwg-bounces@lists.whatwg.org
[mailto:whatwg-bounces at lists.whatwg.org] On Behalf Of gary turner
Sent: Wednesday, May 30, 2007 10:21 PM
To: Henri Sivonen
Cc: WHATWG; Ian Hickson; Gervase Markham
Subject: Re: [whatwg] Style sheet loading and parsing (over HTTP)

Henri Sivonen wrote:
> <snip>
> I was serious. If you want to display plain text in the browser content 
> area, it seems that prepending "<plaintext>" and sending it as text/html 
> is more likely not to invoke sniffing than sending it as text/plain. 
> This use case doesn't require an end tag.
Ah.  That, "prepending", gives me a better idea of your meaning.  Eg., a 
file, source.html, containing
would not be sniffed by IE, and would be rendered as plain text.  Where 
normally, the file, as source.txt, with its text/plain content type, and 
without the <plaintext> tag, would be sniffed by IE and rendered as an 
html document.

If a UAs were to simply honor the server response header, it would 
obviate the need for such an inelegant work-around.

Thanks for the clarification.


Anyone can make a usable web site. It takes a graphic
designer to make it slow, confusing and painful to use.
Received on Thursday, 31 May 2007 03:20:07 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:55 UTC