Re: LINK TYPE=override/type

Benjamin Franz (snowhare@netimages.com)
Fri, 23 Jan 1998 09:17:48 -0800 (PST)


Date: Fri, 23 Jan 1998 09:17:48 -0800 (PST)
From: Benjamin Franz <snowhare@netimages.com>
To: www-html@w3.org
In-Reply-To: <199801231645.JAA00146@underworld.bigpic.com>
Message-ID: <Pine.LNX.3.96.980123090736.27647A-100000@ns.viet.net>
Subject: Re: LINK TYPE=override/type

On Fri, 23 Jan 1998, Neil St.Laurent wrote:

> At the moment it seems like the TYPE in LINK is absolutely pointless 
> since I have to download all of the STYLESHEETS anyways to get their 
> correct 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.

And the answer to the question of 'which overrides which' is: The TYPE and
the Content-Type must match. If they don't its an *ERROR*. Error
handling is agent specific and should not be relied on under any
circumstances. FWIW - Netscape appears to assume that if the Content-Type
is wrong, its JSSS or Javascript. Period.

-- 
Benjamin Franz