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

RE: The <link> element

From: Ian Hickson <py8ieh@bath.ac.uk>
Date: Thu, 24 Jun 1999 18:21:18 +0100 (BST)
To: Chris Wilson <cwilso@microsoft.com>
cc: www-html@w3.org, Nicolas Lesbats <nlesbats@etu.utc.fr>
Message-ID: <Pine.GSO.4.04.9906241815120.128-100000@ss1.bath.ac.uk>
On Thu, 24 Jun 1999, Chris Wilson wrote:

>>> [HTML]	<link rel="next" href="next.html" title="Title of Next">
>>> [CSS2]	head { display: block } /* display the document head */
>>> 	link:before { content: attr(title) } /* display the 'title' */
>>> *Will* a *conformant* browser render the expected rendering ?
>> Yes.
> Actually, not necessarily, unless you're referring to XHTML. HTML
> processors may treat BODY as the root of rendered content, and HEAD
> content may be unrenderable.  Read the caveats in CSS2 carefully.

Good point. Let me rephrase my "yes" then:

It would be correct if it did, and browsers supporting _all_ of their
media type would. However, it is an optional feature.

>>> In particular, will the generated content really be a link ?
>> Good question. I suppose that logically it should be.
> Perhaps, but it won't be just based on the stylesheet - CSS cannot set
> up hyperlinks.  This semantic would have to be cooked in the UA.

Or by XLink, yes. Of course, it is not yet a REC either...

Ian Hickson
: Is your JavaScript ready for Nav5 and IE5?
: Get the latest JavaScript client sniffer at 
: http://developer.netscape.com/docs/examples/javascript/browser_type.html
Received on Thursday, 24 June 1999 13:21:24 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:50 UTC