W3C home > Mailing lists > Public > whatwg@whatwg.org > February 2008

[whatwg] Proposal for a link attribute to replace <a href>

From: Krzysztof Żelechowski <giecrilj@stegny.2a.pl>
Date: Thu, 28 Feb 2008 16:35:05 +0100
Message-ID: <1204212905.6612.13.camel@a1dmin.vola.spe.com.pl>

Dnia 27-02-2008, ?r o godzinie 23:25 +1100, Shannon pisze:

> ---LINK with block-level or interactive content---
> This proposal would circumvent <A>'s main limitation which is its 
> requirement to not wrap block-level elements or 'interactive' content. 
> The HTML5 draft requires it wrap 'phrasing content' (essentially 
> paragraphs) and not wrap 'interactive' content (such as other 
> hyperlinks) however I see no reason why a link attribute should require 
> these limits. Links would simply cascade as in the following example:
> 
> <table link="alphabet.html" title="Alphabetical List">
>     <tr>
>        <td>A</td>
>        <td>B</td>
>        <td link="c.html" title="More about C">C</td>
>        <td>D</td>
>     </tr>
> </table>

Tables should be used to present tabular data.  
Tabular data is something the user may want to meditate or to copy; 
their content cannot be grasped in a glance.
Hyperlinked text should be a concise description 
of the content of the other page; 
a table does not meet that requirement.
This design violates the least surprise principle.

> 
> In the example above clicking anywhere on the table except 'C' brings up 
> a generic page, whereas 'C' has dedicated content. The following nested 
> links would also be valid:
> 
> <span link="foo.html">click anywhere on this line except <b 
> link="bar.html" title="Go to bar instead">here</b> to visit foo.</span>

It would be difficult to style a hyperlink within a hyperlink; 
moreover, a hyperlink that contains another hyperlink is not concise, 
see above.

Chris
Received on Thursday, 28 February 2008 07:35:05 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:39 UTC