W3C home > Mailing lists > Public > www-html@w3.org > December 1999

RE: Navigation Tag

From: David Wagner <dwagner@kevric.com>
Date: Wed, 8 Dec 1999 10:06:38 -0600
Message-ID: <C9B23C6D1899D21188F600C00D009F8606ED42@KEVRICSA1>
To: "www-html@w3.org" <www-html@w3.org>
>Specify that a browser is recommended to implement LINK elements using
>a browser-specific document-independent user interface, ignoring the
>content of the element, but may alternatively just render the content of
>the element (and ignore the attributes of LINK). Naturally older browsers
>(such as all current browsers) would do the latter.
Alternately, since a elements may contain a rel attribute, UAs could choose 
(according to some priority system) to render only one of a set of elements 
with the same rel attribute value.  UA behavior when elements set different 
hrefs for the same rel would, I suppose, be undefined.  (I think this would 
be an error for most relationships.)  Authors should specify related 
documents as link elements if they should be rendered by the UA, and in 
meta elements if they should not.
> Allow the LINK element in the document body, and make it a container.
> Example:
> <link rel="next" href="sec7.html" title="Section 7: Hypermystics">
> <a href="sec7.html"><img alt="next" src="arrow.gif"
> title="Section 7: Hypermystics"></a>
></link>
>...
>To be useful, this change should be accompanied with a specification of
>a minimum set of REL values recognized by browsers which use the
>recommended implementation.
Is this redundancy needed when the rel attribute may be specified directly 
on the a element?  UA behavior could still be as you describe, provided the 
rel of an a element is specified as one of the values in the minimum set. 
 A simpler solution may be to define UA behavior when a rel attribute is 
specified for an anchor.
-David
Received on Wednesday, 8 December 1999 11:08:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:15:40 GMT