- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 24 Sep 2009 23:23:27 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7724
Summary: I would like to know: what is to become of the A
element’s NAME attribute? I validated a HTML5 website
that I am working this Wednesday (2009-09-23) which
contained an A element with a NAME attribute: the W3C
Markup Validator did not mind one bit. Howe
Product: HTML WG
Version: unspecified
Platform: Other
URL: http://www.whatwg.org/specs/web-apps/current-
work/#reviewCommentText
OS/Version: other
Status: NEW
Severity: normal
Priority: P3
Component: HTML5 spec bugs
AssignedTo: dave.null@w3.org
ReportedBy: contributor@whatwg.org
QAContact: public-html-bugzilla@w3.org
CC: ian@hixie.ch, mike@w3.org, public-html@w3.org
Section: http://www.whatwg.org/specs/web-apps/current-work/#reviewCommentText
Comment:
I would like to know: what is to become of the A element’s NAME attribute? I
validated a HTML5 website that I am working this Wednesday (2009-09-23) which
contained an A element with a NAME attribute: the W3C Markup Validator did not
mind one bit. However, today (25-09-25), the W3C Markup Validator is showing
this as an error! For the same page, html5.validator.nu is marking each
occurrence with a warning, but still showing an overall pass. I think that for
reasons of backward compatibility, the NAME attribute SHOULD be kept in the
HMTL5 spec. Older UAs of the Netscape 4 generation do not support the ID
attribute as a fragment identifier, and I think that, solely in the interests
of supporting legacy browsers, the NAME attribute should remain in the spec
(maybe marked as deprecated). Thank you for your time, and keep up the good
work! Regards, Jordan Clark <http://www.jdclark.org/> <mail@jdclark.org>
Posted from: 82.11.218.55
--
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 Thursday, 24 September 2009 23:23:41 UTC