Re: LINK TYPE=override/type

Ian Graham (igraham@smaug.java.utoronto.ca)
Thu, 22 Jan 1998 11:01:09 -0500 (EST)


From: igraham@smaug.java.utoronto.ca (Ian Graham)
Message-Id: <199801221601.LAA11753@smaug.java.utoronto.ca>
To: www-html@w3.org
Date: Thu, 22 Jan 1998 11:01:09 -0500 (EST)
Subject: Re: LINK TYPE=override/type

This issue come up wherever (i) TYPE is used to indicated remote
resource type, which is the case for LINK, A, SCRIPT, and OBJECT 
(at least so far),  or (ii) when META is used to define the default
script, or charset type for a given document.  Needless to say,
the override order should be the same in all cases. 

I believe that tradition (and common sense) say that HTTP-provided
header information should override anything stated in the referring
markup element, since the header contains a 'real-time' definition 
of the HTTP message payload, which contains a lot of payload-related
information in addition to mime type.

On a practical level, I don't believe that TYPE, in any of the above 
contexts, is supported by current browsers -- does anyone know of 
examples where TYPE is supported?

Ian
> 
> Neil St.Laurent wrote:
> 
> > <LINK REL="Something" HREF="somwhere" TYPE="content/type">
> >
> > Does the TYPE here override any returned type from the HTTP
> > connection?
> 
> In the summary about META and charset [1], the user agent must
> first look at the server header, next at any META http-equiv
> declaration, and last at any charset attributes later in the
> document. It doesn't quite answer your question, but might be
> a model for an answer if none exists.
> 
> [1] <http://www.w3.org/TR/REC-html40/charset.html#h-5.2.2>
> 
> Susan Lesch
> 
>