Re: LINK TYPE=override/type

> No, it is *very* useful. It is a guide to the browser which stylesheets
> (scripts, fonts, proprietary extensions, whatever) it can handle and
> should load and which it should just skip because it can't do anything
> meaningful with them anyway. Thus when a browser encounters:
> <LINK rel=stylesheet type="text/css"   href="/stylesheets/default.css">
> <LINK rel=stylesheet type="text/jsss"  href="/stylesheets/default.jsss">
> <LINK rel=stylesheet type="text/xsl"   href="/stylesheets/default.xsl">
> <LINK rel=stylesheet type="text/dsssl" href="/stylesheets/default.dsssl">
> it *doesn't* try to load the stylesheets it can't deal with anyway..

But one of the arguments is that the HTTP header is the authoratative 
answer for the Content-Type, this would mean that the browser would 
have to at least get the HEAD of the above documents to verify 
whether the TYPE is correct or not.

If HTTP is authoratative then TYPE is a pointless attribute when 
using HTTP.
__  __  __  __  __  __  __  __  __  __  __  __  __  __  __  __  __
 Mortar: Advanced Web Development      <http://mortar.bigpic.com/>
 Neil St.Laurent                     <mailto:stlaurent@bigpic.com>
 Big Picture Multimedia                            +1.403.265.8018

Received on Friday, 23 January 1998 13:04:06 UTC