content-type sniffing, and other topics in WhatWG chat (the purpose of standards, plugins, accessibility, and other topics)

[Larry Masinter-3]

Some parts of this message have been removed. Learn more about Nabble's security policy.

I thought I made some progress on uncovering the justification for content-type sniffing application/postscript, at least for Mac Safari users there is a postscript viewer that does something more useful with sniffed postscript (labeled as text/plain) than it would with text/plain itself or application/octet-stream. 

 

The conversation is a little hard to wade through, but suggested reading for other nuggets:

 

http://krijnhoetmer.nl/irc-logs/whatwg/20090927

 

Larry

--

http://larry.masinter.net

 

[Julian Reschke]

Larry Masinter wrote:

>
>
> I thought I made some progress on uncovering the justification for
> content-type sniffing application/postscript, at least for Mac Safari
> users there is a postscript viewer that does something more useful with
> sniffed postscript (labeled as text/plain) than it would with text/plain
> itself or application/octet-stream.
>
>  
>
> The conversation is a little hard to wade through, but suggested reading
> for other nuggets:
>
>  
>
> http://krijnhoetmer.nl/irc-logs/whatwg/20090927
> ...

Related to this: I'd be interested to hear from people looking just at
the words in HTML5 whether they think content type sniffing is required
or not.

BR, Julian