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

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

From: Kristof Zelechovski <giecrilj@stegny.2a.pl>
Date: Wed, 30 Jul 2008 20:55:56 +0200
Message-ID: <83D7D412726F41E58C9AD210944CBE59@POCZTOWIEC>
By the current spec, the Anchor element is phrasing content, which is a
special case of flow content.  Did you mean "transparent content" instead?
EC! I cannot see any "inline content" in HTML5, at least not in 3.4.1 where
content models are defined.

-----Original Message-----
From: Ian Hickson [mailto:ian@hixie.ch] 
Sent: Wednesday, July 30, 2008 1:50 PM
Cc: WhatWG
Subject: Re: [whatwg] Proposal for a link attribute to replace <a href>

On Sun, 1 Jun 2008, Ernest Cline wrote:
> Backwards compatible with some user agents but not with the specs.  The 
> following fragment has never been valid according to the specs in any of 
> HTML 1.0, 2.0, 3.2, or 4, or the current draft of HTML 5, despite <a>, 
> <h3>, and <p> appearing in all of them.
> <a href="foo.html">
>  <h3>Heading</h3>
>  <p>Text</p>
> </a>
> The specs have always called for <a> to only have inline content save 
> that for some reason, HTML 2.0 did allow <h1> to <h6> inside <a> though 
> that was not recommended, and that was reverted back to inline only in 
> 3.2.
> While changing the specs to match user agent behavior is a possibility, 
> it is not one that should be taken lightly. (Nor should adding a new 
> flow content hyperlink element, be taken lightly either.)

Changing the specs to match user agent behavior is the whole way HTML5 
works, so that's not a big problem. The problem is that the current parse 
model results in odd behaviour if we allow <a> as a flow-content element.
Received on Wednesday, 30 July 2008 11:55:56 UTC

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