This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 22064 - [HTML]:
Summary: [HTML]:
Status: RESOLVED INVALID
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: Macintosh MacOS X
: P2 minor
Target Milestone: ---
Assignee: Edward O'Connor
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-16 14:36 UTC by Robert
Modified: 2013-05-17 03:18 UTC (History)
5 users (show)

See Also:


Attachments

Description Robert 2013-05-16 14:36:59 UTC
"If there is an a element in the DOM that has a name attribute whose value is exactly equal to fragid (not decoded fragid), then the first such element in tree order is the indicated part of the document"

There is no corresponding documentation in the portion of the spec for the "a" element indicating that a "name" attribute is legal, or what its semantics might be. (http://www.w3.org/html/wg/drafts/html/master/text-level-semantics.html#the-a-element)
Comment 1 Boris Zbarsky 2013-05-16 14:42:02 UTC
The documentation you seek is at http://www.w3.org/html/wg/drafts/html/master/obsolete.html#obsolete in the paragraph starting "Authors should not specify the name attribute on a elements."
Comment 2 Edward O'Connor 2013-05-16 19:11:46 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the Editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the Tracker Issue; or you may create a Tracker Issue
yourself, if you are able to do so. For more details, see this document:

   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: No change.
Rationale: That's because <a name> isn't conforming.
Comment 3 Robert 2013-05-17 01:57:57 UTC
Oughtn't the reference to the "name" attribute be removed from the algorithm, in that case? It's still there, as of the 17 May 2013 nightly draft. (http://drafts.htmlwg.org/html/master/browsers.html#the-indicated-part-of-the-document)

(In reply to comment #1)
> The documentation you seek is at
> http://www.w3.org/html/wg/drafts/html/master/obsolete.html#obsolete in the
> paragraph starting "Authors should not specify the name attribute on a
> elements."
Comment 4 Boris Zbarsky 2013-05-17 02:12:44 UTC
Robert, the specification has two sets of requirements:

1)  Requirements for page authors.  In this case that's "Do not use <a name>".

2)  Requirements for UA implementors.  In this case that's the text you quote in
    comment 0.

The text for UA implementors can't go away, since there are lots of existing sites, dating back well over a decade now, that depend on that behavior.