[whatwg] Content-Type (was Style sheet loading and parsing (over HTTP))

Anne van Kesteren annevk at opera.com
Wed May 23 01:07:50 PDT 2007

On Wed, 23 May 2007 04:05:26 +0200, Sander Tekelenburg <st at isoc.nl> wrote:
> Anne, you seem to mean to refer to Style Sheets's Content-Types only, but
> given some of the responses, and some other discussions about  
> Content-Type, I
> take the liberty to interpret this as a more general argument against
> Content-Type.
> At 10:44 +0200 UTC, on 2007-05-22, Anne van Kesteren wrote:
>> For compatibility with the web it seems important to simply ignore
>> Content-Type in all modes.
> I'm confused about "in all modes" in this context. I thouht the idea was  
> to do away with modes altogether?

Standards and quirks mode I meant. Firefox sort of "respects" the  
Content-Type in standards mode but not really. Because we implemented  
something that did completely respect it in standards mode we break  
sites... Go figure.

> With Content-Type, one can serve HTML, CSS, PHP, etc. as text/plain.  
> Useful to provide example code. I'm sure there are more use cases where  
> there is no single correct interpretation other than the one the author  
> specifies. Should we really make that impossible?

This was about loading style sheet resources. User agents know when  
they're doing that. The same goes for loading image resources (from <img>  
or background-image).

Anne van Kesteren

More information about the whatwg mailing list