Re: [whatwg] Sanctity of MIME types
On 12/6/06, Sam Ruby <[EMAIL PROTECTED]> wrote: How was it fixed? It was fixed in a way that covers mis-sniffed feed content specifically. That is, content that was sniffed as a feed but isn't one, like that Atom template or some FOAF files, are displayed correctly. These are edge cases. Both so that Ian's eventual text can be consistent with the fix, and for my edification as I would love to be able to directly view my test cases again: Your test cases are a different bug: "correctly" sniffed feeds that you don't want sniffed. Unfortunately, I can't agree that the MIME type "text/plain" carries as strong a message as it used to. It would be possible to turn off sniffing for some 'text/plain' values if there were a better indicator available. For example, by using a new Content-Disposition value (web compatible because unknown values are treated as 'inline'). -- Robert Sayre
Re: [whatwg] Sanctity of MIME types
Robert Sayre wrote: On 12/5/06, Sam Ruby <[EMAIL PROTECTED]> wrote: I have a request. It would be nice if the sniffing algorithm made an exception for "text/plain". It would be nice, but Use case: http://svn.smedbergs.us/wordpress-atom10/tags/0.6/wp-atom10-comments.php Fixed in FF 2.0.0.1, btw. text/plain sniffing in Mozilla dates from this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=220807 1.120 <[EMAIL PROTECTED]> 2004-01-07 19:56 Work around misconfiguration in default Apache installs that makes it claim all sorts of stuff as text/plain. http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/uriloader/base/nsURILoader.cpp&rev=1.120#289 How was it fixed? Both so that Ian's eventual text can be consistent with the fix, and for my edification as I would love to be able to directly view my test cases again: http://feedvalidator.org/testcases/atom/3.1.1.1/escaped_text.xml - Sam Ruby
Re: [whatwg] Sanctity of MIME types
On 12/5/06, Sam Ruby <[EMAIL PROTECTED]> wrote: I have a request. It would be nice if the sniffing algorithm made an exception for "text/plain". It would be nice, but Use case: http://svn.smedbergs.us/wordpress-atom10/tags/0.6/wp-atom10-comments.php Fixed in FF 2.0.0.1, btw. text/plain sniffing in Mozilla dates from this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=220807 1.120 <[EMAIL PROTECTED]> 2004-01-07 19:56 Work around misconfiguration in default Apache installs that makes it claim all sorts of stuff as text/plain. http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/uriloader/base/nsURILoader.cpp&rev=1.120#289 -- Robert Sayre
Re: [whatwg] Sanctity of MIME types
Ian Hickson wrote: On Mon, 4 Dec 2006, Sam Ruby wrote: Independent of what the specs say *MUST* happen, I'd like people to bring up one or more browsers with a URL from this list, and see if the browser asked them if they wanted to subscribe. Subscribe is not a normal feature associated with text/html, which is the Content-Type that you will find for each. Actually, this is what Web Apps 1.0 will require, I just haven't written the sniffing algorithm yet. This is the placeholder section: http://www.whatwg.org/specs/web-apps/current-work/#navigating Note the mention of RSS/Atom in the first red box. I have a request. It would be nice if the sniffing algorithm made an exception for "text/plain". Use case: http://svn.smedbergs.us/wordpress-atom10/tags/0.6/wp-atom10-comments.php - Sam Ruby
Re: [whatwg] Sanctity of MIME types
On Mon, 4 Dec 2006, Sam Ruby wrote: > > Independent of what the specs say *MUST* happen, I'd like people to > bring up one or more browsers with a URL from this list, and see if the > browser asked them if they wanted to subscribe. Subscribe is not a > normal feature associated with text/html, which is the Content-Type that > you will find for each. Actually, this is what Web Apps 1.0 will require, I just haven't written the sniffing algorithm yet. This is the placeholder section: http://www.whatwg.org/specs/web-apps/current-work/#navigating Note the mention of RSS/Atom in the first red box. -- Ian Hickson U+1047E)\._.,--,'``.fL http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
[whatwg] Sanctity of MIME types
Here's a random half dozen examples, picked to show a bit of diversity: http://beta.versiontracker.com/mac/osx/home-edu/updates.rss http://city.piao.com.cn/rss.asp?85 http://feuerwehr-melle-de.server13031.isdg.de/index.php?id=199 http://hesten.innit.no/hru/rss.php?START=0&STOP=3 http://httablo.hu/pages/rss.php http://skopjeclubbing.com.mk/rss_djart.asp Independent of what the specs say *MUST* happen, I'd like people to bring up one or more browsers with a URL from this list, and see if the browser asked them if they wanted to subscribe. Subscribe is not a normal feature associated with text/html, which is the Content-Type that you will find for each. The point is not to label these guys bozos (as I said in previous messages, bozos outnumber you). But to get you to consider what browsers can, and will, do. In these days of GreaseMonkey and its brethren, the client is king. - - - Where does this leave HTML5? I am of the opinion that HTML5 should describe a set of rules that a compliant HTML5 parser should follow. The MIME and DOCTYPEs specified in the document should be recommendations. Something outside of the parser may chose to dispatch based on this information, but that's outside of the control of the parser. IMHO, the parser itself shouldn't complain when it finds a HTML4 DOCTYPE, or an XHTML2 DOCTYPE for that matter. Of course, a lot more HTML4 documents would be valid HTML5 than XHTML 2 documents. - Sam Ruby
