Should I make HTML Anchors with 'name' or 'id'?
When one wants to refer to some part of a webpage with the "http://example.com/#foo" method, should one use
<h1><a name="foo"/>Foo Title</h1>
or
<h1 id="foo">Foo Title</h1>
They both work, but are they equal, or do they have semantic differences?
http://example.com#foo (so without the / before #)
http://example.com#foo and http://example.com/#foo are equivalent as defined in one of the RFCs on URIs.
According to the HTML 5 specification, 5.9.8 Navigating to a fragment identifier:
For HTML documents (and the text/html MIME type), the following processing model must be followed to determine what the indicated part of the document is. Parse the URL, and let fragid be the
So, it will look for id="foo", and then will follow to name="foo"
Edit: As pointed out by @hsivonen, in HTML5 the a element has no name attribute. However, the above rules still apply to other named elements.
You shouldn’t use <h1><a name="foo"/>Foo Title</h1> in any flavor of HTML served as text/html, because the XML empty element syntax isn’t supported in text/html. However, <h1><a name="foo">Foo Title</a></h1> is OK in HTML4. It is not valid in HTML5 as currently drafted.
<h1 id="foo">Foo Title</h1> is OK in both HTML4 and HTML5. This won’t work in Netscape 4, but you’ll probably use a dozen other features that don’t work in Netscape 4.
ids just like name anchors in terms of URL fragments and compatibility of the CSS :target selector. Tested: Chrome 6, Firefox 1.5, IE6, Opera 8.02, Safari 3.1.2, Netscape 7.2, Lynx 2.24, and mobile browsers: Android 2.2, Chrome 26, Dolphin 9.3, Firefox 19, IE10, Safari 4, and Opera Mini 5.1.
I have to say if you are going to be linking to that area in the page... such as page.html#foo and Foo Title isn't a link you should be using:
<h1 id="foo">Foo Title</h1>
If you instead put an <a> reference around it your headline will be influenced by an <a> specific CSS within your site. It's just extra markup, and you shouldn't need it. I'd highly recommend placing an id on the headline, not only is it better formed, but it will allow you to either address that object in Javascript or CSS.
Wikipedia makes heavy use of this feature like this:
<a href="#History">[...]</a>
<span class="mw-headline" id="History">History</span>
And Wikipedia is working for everybody, so I would feel safe sticking with this form.
Also don't forget, you can use this not only with spans but with divs or even table cells, and then you have access to the :target pseudo-class on the element. Just watch out not to change the width, like with bold text, cause that moves content around, which is disturbing.
Named anchors - my vote is to avoid:
"Names and ids are in the same namespace..." - Two attributes with the same namespace is just crazy. Let's just say deprecated already.
"Anchors elements without href atribute" - Yet again, the nature of an element (hyperlink or not) is defined by having an atribute?! Double crazy. Common sense says to avoid it altogether.
If you ever style an anchor without a pseudo-class, the styling applies to each. In CSS3 you can get around this with attribute selectors (or same styling for each pseudoclass), but still it's a workaround. This usually doesn't come up because you choose colors per pseudo-class, and the underline being present by default it only makes sense to remove, which makes it the same as other text. But you ever decide to make your links bold, it'll cause trouble.
Netscape 4 might not support the id feature, but still an unknown attribute won't cause any trouble. That's what called compatibility for me.
a {color:red} it will color both your <a href> links AND your <a name> fragments. You can get around this with pseudo classes a:link {color:red]} or attribute selectors a:not([href]) {color:red;}
<a name="heading1"></a> ... document.html#heading1 without setting the ID, because the ID may clash with another ID on the page. It's a shame they didn't put the name attribute in HTML5.
<h1 id="foo">Foo Title</h1>
is what should be used. Don't use an anchor unless you want a link.
Heads up for JavaScript users: all IDs become global variables under window.
<h1 id="foo">Foo Title</h1>
Just created the JS global:
window.foo
The value of window.foo will be the HTMLElement for the h1.
Unless you can guarantee all values used in id attributes are safe, you may prefer sticking to name:
<h1 name="foo">Foo Title</h1>
window. For example, <div id="open"></div> won't overwrite the function window.open.
There's no semantic difference; the trend in the standards is toward the use of id rather than name. However, there are differences that may lead one to prefer name in some cases. The HTML 4.01 specification offers the following hints:
Use id or name? Authors should consider the following issues when deciding whether to use id or name for an anchor name:
The id attribute can act as more than just an anchor name (e.g., style sheet selector, processing identifier, etc.).
Some older user agents don't support anchors created with the id attribute.
The name attribute allows richer anchor names (with entities).
id anchors to work in Safari for iOS 5, so it's not just browsers that were already "really old" in '09. I had to add names to get my site to work properly on the iPad. This might have been fixed by now, I don't own any iOS 6 devices to check.
id anchors seem to work universally. If this simple example doesn't work on your mobile, I would check the device accessibility settings. (@deathApril Wikipedia mobile site has Javascript that effectively causes the URL fragment to be ignored.)
ID method will not work on older browsers, anchor name method will be deprecated in newer HTML versions... I'd go with id.
In html 5, the id="" attribute defines a unique identifier for an element, which is also an anchor for a fragment link. In previous html standards, the name="" attribute of the <a> element defines an anchor for a fragment link. I recommend something like:<a name="foo" id="foo"></a><h1>Foo Title</h1>
Because support for the id="" attribute is a bit spotty(even though the latest releases of all major browsers support it, the releases that don't aren't more than a few years old[And it's best not to break something if there isn't a good reason to]). It's compatible, & it doesn't style whatever's in the link'd element, for the closing </a> is still outside the element, but it's still valid in all current standards.
Be sure that the name="" and id="" attributes of the <a> element are the same.
name attribute on an anchor tag that was required; placing attributes on an hN or span didn't work.
I have a web page consisting of a number of vertically stacked div containers, identical in format and differing only in serial number. I wanted to hide the name anchor at the top of each div, so the most economical solution turned out to be including the anchor as an id within the opening div tag, i.e,
<div id="[serial number]" class="topic_wrapper">
The second sample assigns a unique ID to the element in question. This element can then be manipulated or accessed using DHTML.
The first one, on the other hand, sets a named location within the document, akin to a bookmark. Attached to an "anchor", it makes perfect sense.
Just an observation about the markup The markup form in prior versions of HTML provided an anchor point. The markup forms in HTML5 using the id attribute, while mostly equivalent, require an element to identify, almost all of which are normally expected to contain content.
An empty span or div could be used, for instance, but this usage looks and smells degenerate.
One thought is to use the wbr element for this purpose. The wbr has an empty content model and simply declares that a line break is possible; this is still a slightly gratuitous use of a markup tag, but much less so than gratuitous document divisions or empty text spans.
wbr: w3.org/TR/html-markup/wbr.html Use <wbr id="foo" /> rather than <a name="foo"></a>
How about using name attribute for old browsers and id attribute to the new browsers. Both options will be used and fallback method will be implemented by default!!!
It's not about support right now, because who would care in 2021 about older browsers than IE6?
Notice that Stackoverflow is still using anchor and 'name' attribute instead of 'name' attribute.
Why?
Because you:
can't have two values for id on SINGLE element.
#sample { color: red; }
Ok, you can say you can use 'class' for the sake of things like that.
It's true but if there is only single element that needs to be styled on your site then you shouldn't use class.
Why?
Because if you use CSS selector #idName and web browser finds that element it won't look further. It speeds loading of your website.
If you use .class it needs to look for every place of your DOM because web browser doesn't know if you had used .class once or more times.
You can't start 'id' value with number if you want to style it in CSS or use JS to parse it. You can however start 'name' value with number.
The whole "named anchor" concept uses the name attribute, by definition. You should just stick to using the name, but the ID attribute might be handy for some javascript situations.
As in the comments, you could always use both to hedge your bets.
Follow WeChat
Success story sharing
Want to stay one step ahead of the latest teleworks?
Subscribe Now相似问题
- What are valid values for the id attribute in HTML?
- How can I change an element's class with JavaScript?
- Where should I put <script> tags in HTML markup?
- How can I detect changes in location hash?
- How to make a div 100% height of the browser window
- How do I create an HTML button that acts like a link?
- Why does HTML think “chucknorris” is a color?
HuntsBot,a one-stop outsourcing task, remote job, product ideas sharing and subscription platform, which supports DingTalk, Lark, WeCom, Email and Telegram robot subscription. The platform will push outsourcing task requirements, remote work opportunities, product ideas to every subscribed user with timely, stable and reliable.
<h1 id="foo">Foo Title</h1>works even in IE6 and is part of HTML 4.01 specificationname="foo"and aid="foo"(independently of their order within the page), Chrome and Firefox will jump to theid, but IE (tested in 11) and Edge will jump to thename