W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > March 2011

[Bug 12334] make <a name> valid again in HTML5

From: <bugzilla@jessica.w3.org>
Date: Fri, 18 Mar 2011 17:58:24 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Q0dwO-00014d-Vj@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12334

Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |xn--mlform-iua@xn--mlform-i
                   |                            |ua.no

--- Comment #1 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> 2011-03-18 17:58:24 UTC ---
(In reply to comment #0)
> I am then suggesting (a) to revert the semantics of <a> to the
> html4 semantics: it's the source of an hyperlink and/or a named
> anchor (b) to make <a name> valid again in html5.
> I would not mind if a note is added asking web authors to prefer the
> id attribute on an another element.

ONE: I support the view that the definition of <a> is not optimal. If I
remember correctly, it says that an <a> without @href, is "a place were there
could have been a link if it had been relevant".

TWO: But regardless of the definition: inside BlueGriffon, why don't you just
convert <a name="*"> into <a id="*"> ?

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 18 March 2011 17:58:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 18 March 2011 17:58:27 GMT