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

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

From: Ernest Cline <ernestcline@mindspring.com>
Date: Mon, 2 Jun 2008 22:04:31 -0400 (GMT-04:00)
Message-ID: <9900645.1212458671611.JavaMail.root@mswamui-bichon.atl.sa.earthlink.net>


-----Original Message-----
>From: Anne van Kesteren <annevk at opera.com>
>Sent: Jun 2, 2008 5:39 AM
>
>On Mon, 02 Jun 2008 05:26:40 +0200, Ernest Cline  
><ernestcline at mindspring.com> wrote:
>>> The <a> element can already do this and it would be backwards  
>>> compatible.
>>
>> Backwards compatible with some user agents but not with the specs.
>
>Sure, but <anchor> is not backwards compatible with specs or user agents.
>

That might be a reason to adjust the spec for <a> to have it match current behavior, but in my opinion it would be better to provide for the block/inline distinction to be handled with recourse to CSS by having separate elements as is the case for <div>/<span>.  There are alternatives to obtain this behavior in old browsers without using <a> in a block context, so the loss of backward compatibility would be a minor issue at most.

That said, adjusting the spec to have <a> follow current behavior would be better than leaving the spec as it is and not have any spec compliant method to provide a block level hyperlink without the use of scripting.
Received on Monday, 2 June 2008 19:04:31 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:03 UTC