Web developers these days are often expected to know and work in multiple languages. As a result, it's tricky to learn everything a language has to offer and easy to find yourself not utilizing the full potential of some more specialized but very useful tags.
Unfortunately we haven't been tapping into the full potential of these more obscure HTML tags as of late. But it's never too late to get back into the game and start writing code that taps into the power of some under-used tags.
Here are ten of some of the most underused and misunderstood tags in HTML. While they might be less familiar, they're still quite useful in certain situations.
Glen Stansberry is a web developer and blogger. You can read more tips on web development at his blog Web Jackalope or follow him on Twitter.
1. <cite>
All of us will be familiar with the <blockquote> tag, but did you know about <blockquote>'s little brother <cite>? <cite> allows you to define the text inside of the element as a reference. Typically the browser will render the text inside of the <cite> tag in italics, but this can be changed with a touch of CSS.
The <cite> tag is really useful for citing bibliographic and other site references. Here's an example of how to use the cite tag in a paragraph:
David Allen's breakthrough organization book Getting Things Done has taken the web by storm.
2. <optgroup>
The <optgroup> tag is a great way to add a little definition between groups of options inside a select box. If you needed to group movie listings by time, for example, then it would look like this:
Live demo:
This allows the select list to visually separate the movie listings.
3. <acronym>
The <acronym> tag is a way to define or further explain a group of words. When you hover over text that has the <acronym> tag used, a box appears below with the text from the title tag. For example:
The microblogging site Twitter has recently struggled with downtimes.
Live demo:
SEO is full of trickery and magic.
4. <address>
The <address> tag is quite an obscure little tag, but that doesn't mean it isn't useful! As the name implies, <address> allows you to semantically markup addresses in HTML. The nifty little tag will also italicize all of the data within the brackets, though the style can easily be changed through simple CSS.
Glen Stansberry
1234 Web Dev Lane
Anywhere, USA
5. <ins> and <del>
If you're wanting to display editing revisions with with markup, <ins> and <del> are just the ticket. Like the name implies, <ins> highlights what's been added to the document with an underline, and <del> shows what's been taken out with a strikethrough.
John likes LOVES his new iPod.
Live demo:
John likes LOVES his new iPod.
6. <label>
Form elements seem the easiest to forget when marking up a document. Of the form elements, one of the most forgotten is the <label> tag. Not only is it a quick way to note the label's text, the <label> tag can also pass a "for" attribute to specify which element is to be given the label. Not only are these <label> tags great for styling, they also allow you to make the caption clickable for the associated element.
7. <fieldset>
Fieldset is a nifty little attribute that you can add to your forms to logically group form elements. Once applied the <fieldset> tag draws a box around the elements within the fieldset. Bonus points for adding a <label> tag within the fieldset to define the title of the group.
Live demo:
8. <abbr>
The <abbr> tag is much akin to the <acronym> tag, except the <abbr> tag is only used to define abbreviated words. Just like <acronym>, you define a title within the tag. When a visitor hovers over the abbreviated text, the full definition appears below. The <abbr> tag is rarely used, but the benefits are many for screen readers, spellcheckers and search engines.
Sgt. Pepper's Lonely Hearts Club is my favorite album.
Live demo:
Sgt. Pepper's Lonely Hearts Club is my favorite album.
9. rel
Rel can be an insanely useful attribute, as any HTML element can have a rel applied to it. It's helpful for passing extra variables that aren't otherwise specified. This is helpful when using Javascript with your HTML. If you have a link that you want to edit inline, you might add:
The Javascript might be looking for a link with the rel attribute "clickable", and it knows to apply some Ajax and allow it to be edited inline. This is one of many techniques you can use with the rel attribute, as the possibilities are endless.
10. <wbr>
The <wbr> tag is an incredibly obscure tag. To be honest, I doubt many of you have come into contact with the tag, as it's hardly ever used. (Truthfully, I hadn't seen the tag before I started researching this article.) Essentially, the tag allows you to specify a place where you think a line break might be useful, but only if needed. This tag is unique as it relies on the discretion of the browser to insert the linebreak, if needed. It's perfect for creating layouts that you want to avoid having horizontal scrollbars.
If you were wanting to achieve the same effect but without using the <wbr> tag, you could also try or . It should be noted that none of these tags have full support across all browsers. To see which browsers support the tags check out this article by Quirksmode.
How do you say Supercalifragilisticexpialidocious?
Related Posts
Check out some more great tutorials and articles that you might like
Woooow i’m the first one unbelievable ,
nice tuts by the way some of those tags i see them for the first time in this tut.
does anyone knows if this site is going to post any .net tut ??
I use rel on every site I build, as in rel=”ext” to define a link as being to an external website. Javascript picks this up and opens the link in a new window (rather than using target=”_blank” which is depricated in Strict).
@Jonny Haynes
This is true most of the time, but there are plenty of occasions where you definitely want to force the user to open a new tab/window.
The most common one is when you have a site targeted at less computer-savvy users and you have a link that, if opened in the same window, would interrupt a set of steps they’re going through.
For example, I maintain a website where people can post and search for apartments (much like Craigslist). The apartment posting process has 7 steps, each on its own page. Many elderly folks with extra rooms in their house post apartments here, and many of them aren’t great with computers, so on each page, we have a link to a video tutorial that explains how to fill out the current page.
If a user clicked the video tutorial link on step 4 of 7, and it opened in the same page, they would need to navigate back to their half-complete listing after watching the tutorial. While this would obviously be no problem for you or me, it can be very confusing for someone who is unfamiliar with computers.
Instead, we open the video in a new window, and include text saying “When you’re done watching this tutorial, close this window to return to your listing.” If we didn’t force open a new window, many non-computer-savvy users (the very people we’re trying to help with usability/accessibility practices in the first place) would end up much more confused than they do now.
Why not just use something like ‘Lightbox’ or ‘Highslide’ (with a non-javascript fall back) with an iframe inside it? That way, they never have to leave your site.
We’ve done that on numerous occasions for things you’ve already mentioned.
Joe Wiggles March 25th
I work at a newspaper site and we always use “target=”_new” for our advertisements. We’ve found that many times when a user clicks off of our site to another they will lose track of where they were originally and go on to other things. Our strategy is to keep our site in the background or on another tab so that hopefully when the user closes this new window, our site will still be easily available. No complaints so far.
Informative post, however wouldn’t it be more appropriate if the examples were in XHTML? I don’t think anyone that codes uppercase HTML without quotes around attributes is going to use any of these tags.
What are you talking about? IE does support XHTML.
william March 24th
IE DOES SUPPORT XHTML if the XHTML is CODED in HTML COMPATIBLE MODE and you use the right DTS example
Why?, because it will be close to the new standards, and xhtml is an step in the right direction you will have the content easier to update and migrate
IE doesn’t support XHTML (not even IE8) so what you do is pass the XHTML code as HTML (http://www.w3.org/TR/xhtml-media-types/#text-html) and all browsers will parse the page as invalid HTML with a bunch of unnecessary forward slashes and unclosed tags, a so called “tag soup”. XHTML is good, but only if you use it in the right way with the mediatype “application/xhtml+xml” (http://www.w3.org/TR/xhtml-media-types/#application-xhtml-xml) in which case IE users will now see the page but will be asked to download it. The best solution at the moment is to use HTML4strict. Nobody stops you from using lowercase tags and quotes around attributes, it’s actually good practice (http://www.webdevout.net/test?html4-good-practice).
If you want to learn more, read this article: http://www.webdevout.net/articles/beware-of-xhtml
It’s long, but it’s worth the time since most people don’t really understand what doctype they are using.
I thought fieldset is required for forms when using the xhtml strict doctype? It should be in your forms if you use xhtml.
Actually, I always use fieldset, legend and labels for my forms.
And another one cool (rare?) tag I love for forms is button instead of input type=”submit”. It’s so much easier to style with css and allows icons in the buttons. It validates, and I have yet to find problems with it. But w3c doesn’t recommend using it.
Didn’t know about optgroup and wbr though, thanks!
I agree that the button tag is great, and especially to style, the trouble is that different browsers (IE grrrr) interpret it differently if its placed in an HTML form.
is mostly fine, until you have a form with multiple submit buttons.
IE6 only recognises the value of the last submit button in your form.
So, if you have a Save button, followed by a Cancel button, all buttons will take on the value of Cancel.
It’s most unfortunate that you mis-used half of the items in this post.
cite should be used when you’re actually _citing_ something from a source, like if you’re using a blockquote or q element.
optgroup should contain a set of options, not be closed before the options. Your “live demo” doesn’t show any visual difference because of your improper usage.
acronym is used for acronyms. Defining acronym, “a word formed from the initial letters of the several words in the name”… The usage in your example just hurts my brain.
According the HTML specs, address is used to denote the address of the page creator: “The ADDRESS element may be used by authors to supply contact information for a document or a major part of a document such as a form. This element often appears at the beginning or end of a document.” See: http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.6
Pretty sad that you didn’t use labels in your fieldset example.
The abbr example is a better example of an acronym. abbr, or Abbreviation is a “shortened form of a word” like ‘management’ -> ‘mgmt’.
rel should be used to describe the relationship of the text to the current tag. W3C says, “This attribute describes the relationship from the current document to the anchor specified by the href attribute. The value of this attribute is a space-separated list of link types.”
wbr is not in any HTML spec. It is a non-standard tag that was added by Netscape, and later dropped around Netscape 4 or 5.
I’m incredibly disappointed by the inaccuracies that you’re giving people who might not know better.
seriously, way to go and set web development back to the 90s with this tutorial. I’m kind of appalled at Net Tuts for allowing this content to go up. Makes me wonder what other crap they’ve let slip through their hands.
Thanks, you have saved me a lot of typing, I was just about to start writing why my brain melted while trying to go through this article.
The only thing I would add is that rel is not a tag.
I think it’s really weird that nettuts accepts articles like this one which was obviously just written for money, not for teaching people. Shame on you glen.
Glen’s articles are unfortunately usually of poor quality. I tend to browse through the comments to find there is always someone like Paul serving out cold hard facts.
Anonymous March 24th
Thank you for posting the clarifying information. I can’t find anything to confirm that “rel” is a valid attribute on ALL html elements. I only see it applied to A elements.
But c’mon, your example of what a real abbr is (management => mgmt) is exactly how he used it! Sergeant => Sgt. His use of the abbr tag works just fine.
But the acronym usage (Twitter??) is totally wrong. It only would have been correct if Twitter stood for something.
It appears though, that acronym and abbr were listed for the effect of providing a title on hover… A title on any element at all will provide the hover tool tip. A better use for the Twitter case would be <span title=”Found in 2006″>Twitter
Sean: The article was corrected for abbreviation and optgroup after my comment was made.
I really try not to be harsh when dishing out the facts, but I expected a little error checking by a professional before something like this would be posted.
Agreed on author’s unneeded mention of wbr. It’s messing up pages on one blog of mine big-time because it’s automatically inserted by the CMS (there is no end-user control over it unless I go and rewrite some Perl just to make myself happy). It’s inserted to break up long URLs and it does NOT validate as XHTML Transitional, so I imagine it doesn’t validate in Strict, either. My frustration with it is endless.
The radio tags in example 7 are not coded correctly; they should have the same name so that only ONE option at a time can be selected.
Furthermore, the FIELDSET example does not show a border (like it may by default) because there is a CSS reset on this page (e.g. borders are set to 0).
Agreed. Honestly, this article should be pulled or significantly edited – right now it’s simply too inaccurate to be of use.
And on WBR, as Paul mentioned it’s a non-standard, deprecated tag (so shouldn’t be in this list at all), but on top of that it’s used wrong – WBR would only go inside a NOBR tag, which is deprecated as well (replaced by CSS whitespace: nowrap).
Points for encouraging use of things like ABBR, but mistakes are just stacked on mistakes in this article.
Usage instead of wbr could be the validating and which almost do the same and wouldn’t need to be inside a NOBR tag or any tag at all. it’s just a break-up technique.
Usage instead of wbr could be the validating [&]shy; and [&]#8203; which almost do the same and wouldn’t need to be inside a NOBR tag or any tag at all. it’s just a break-up technique. delete the [ and ] signs from the content above to actually have it working.
Paul … Agreed. ’bout blew my lid when I saw the semantic abuse of <acronym>. I use <span class=”info” title=” More information here “> for stuff like that. Plus, I’ve even made a pure-CSS popInfo box, if you’ve more information than what might show in bubble-text.
Ugh.. reading that critique turns my stomach for the thousands of ways every developer thinks their way is the right way until another claims they’re wrong. All the while, practically everyone’s work is breaking under some condition… never completely satisfying.
Yeah, fieldset is required and if you are not using it then you aren’t even making forms the right way If you haven’t used it, every site you have done should fail on validation, so hopefully this isn’t too rare…
Required with what version of XHTML? I have validated many pages with forms and never used a fieldset and they have all validated. I am using 1.0 Strict.
Every needs to have some sort of block element wrapping the . You can not, for example, have but you _could_ have:
But this is not the _right_ way of doing this. When specifying a form you should put a WITH a , of course, because s need a block element wrapping them, like this:
Search
But just because you can validate a form by wrapping it with most all block elements(i *believe* can’t wrap it in a blockquote) doesn’t mean it’s right, for example, does this look right?
There are others you could do such as , but that makes no semantic sense. Even makes no sense really. I can understand and though…
Also, XHTML 1.0 is like saying “Hey browser look, it looks like XHTML, but it isnt! HA!”
XHTML really is just fad I have come to find out. I used to use XHTML, and still do where I have to, like WP, but it really is a fad. Unless you are using valid XHTML 1.1 (and declare XML), don’t use XHTML because it’s meaningless.
Damn it, netuts strips out code? Why not just convert it to html entities! It’s only 1 line of code!
Well, my previous comment now looks completely moronic, ok, to get to my point since I can’t actually show examples I guess, and there is no edit button, nor a preview button in site:
you can wrap you inputs in your form with MOST block elements such as p, pre, h1-h6, etc, but having
[h1][input][/h1] or [pre][input][/pre] makes no semantic sense and should not be done! Use
[form]
[fieldset]
[legend]Fieldset group name[/legend]…(inputs here)…
[/fieldset]
[form]
Liam March 24th
Except a site without a fieldset, will validate XHTML Strict.
Are you kidding? did you not real Pauls comments on all the fauls with this article. Following this will only lead your students to destruction. If you want to teach them proper web standards, send your students to http://www.w3schools.com not this article
Your use of the acronym tag is incorrect. It is not meant to define or further explain a group of words, but to provide the user with the ability to see the full name of an acronymic term, such as UNESCO, PETA or NCAA.
In fact, your example of the abbreviation tag should actually use the acronym tag, since NCAA is an acronym. Your description is correct, but the example is far from it.
Examples of abbreviations are:
ea (each)
tbsp (tablespoon)
km (kilometre)
abbr (abbreviation)
LOL. An acronym cannot be pronounced, hence it’s an acronym! Acronyms are pronounced as individual letters. Kevin is right.
LOL is an acronym for laughing out loud.
jason March 24th
NCAA is pronounced as letters but not all acronyms are. NASA and SCUBA are two acronyms that have a proper pronunciation and are not just “Spelled” out. People outside of the USA may not know NCAA (which BTW can be pronounced “N-C-double A” as well)
jim March 24th
NCAA is an initialism. An acronym is pronounced as a word.
Alexander March 25th
“It’s pronounced en-see-aye-aye.”
I believe it’s more like en-see-eh-eh, with a Canadian Prairies accent.
Tzafra March 25th
Most people in the USA probably have no idea that SCUBA is actually an acronym. (Self Contained Underwater Breathing Apparatus).
Actually, that’s not true. Fieldset is not required for XHTML strict. You can wrap your form elements in a simple DIV and it will validate just fine. As long as there is something in between the form and the field elements, it’s fine. For example, visit this page, which I coded a while back, and you’ll see that it validates for Strict but does not have a fieldset on either of the two forms:
all of you, what ever happened to SEMANTICS! Yes, so does wrapping an input with h1 or pre, but no one would do that because, it’s not right, neither is wrapping your entire inner form with p tags or divs!
Apparently opt group doesn’t work in chrome… browsing in it right now and had to open up firefox to see the effect. Although it seems like a pretty nice thing.
And the rel attribute is valid on all tags? Thats nice.
Ya… They must have fixed it… because it works great for me in chrome now. Had me a bit worried for a bit. Its a great article either way, just thought it was a cool tag, glad its not deprecated or anything.
The example you have for the abbr tag is actually an acronym and should have been used with the acronym tag.
I am a little uneasy about using acronym or abbr for anything other than what they are meant for. I worry about screen readers saying that Twitter is an acronym for “Founded in 2006″
I don’t think you are using REL properly either as REL and REV are both attributes of A and LINK and have specific uses. It seems with the example that you give that you might as well just use extra class names.
All the rest of the tags are good to use. wbr and label are both great tags.
Kinda disappointing that NetTuts, which usually has great quality posts, let this one slip with errors, such as:
* optgroup is badly used
* isn’t self closed ( is) and it isn’t standard. Using non-standard elements should be disencouraged.
Yes, we often use the tag, often in combination with the and tags. OK, serioiusly, the acronym tag is handy, and the label tag is pretty useful if you do a lot of form work
The use of the acronym tag is wrong. Twitter has no acronym so it wouldn’t require the use of the acronym tag. An acronym is: “A word formed from the initial parts of a name, such as NATO, from North Atlantic Treaty Organisation, or Commintern, from Communist International.”
it doesn’t need a closing tag in HTML, but you could close it out with </wbr> or just <wbr />.
SelenIT July 7th
Validity of any markup means that it fits the corresponding DTD. No DTD for any version of (X)HTML contains the definition of . So is always invalid, with trailing slash or without it.
The requirement of closing empty tags with slashes is about XML wellformedness, not (X)HTML validity. XHTML pages must be well-formed to be parsed when served with proper content-type (e.g. application/xhtml+xml). In all other cases the well-formedness doesn’t matter at all.
EricTN March 23rd
w3c.org says this in HTML 4.1 discussing acronym and abbr:
Western languages make extensive use of acronyms such as “GmbH”, “NATO”, and “F.B.I.”, as well as abbreviations like “M.”, “Inc.”, “et al.”, “etc.”.
It appears the w3c would’ve wrapped NCAA in an acronym tag rather than an abbr tag.
However the word acronym is not clearly defined; some people believe it’s not an acronym unless you can pronounce it like a word (NATO).
None of the above necesarily means that the suggestions you made for the usage of the tags aren’t good ideas. Sometimes the tags don’t have the best names for what they are best used for.
“2. The abbr and acronym examples are, well… wrong I goofed on those. They should be fixed shortly to show correct examples of acronyms and abbreviations.”
The marquee tag is ‘rare’ because it is both invalid and not professional. I used it a few times while I was initially learning, but if you use it on a website be prepared for ridicule, haha.
Marquee works to some extent in Firefox and Opera. I wrote a very popular tutorial on using it. The target audience was of course people with middle-school taste in design.
Marquee is a great tag. If you want to see it in action just read a lot of LJs and MySpaces where that and the blink tag still abound. Eventually you may get the notion it’s immature and unsightly but I liked it when I was just learning HTML.
MARQUEE tag is not a part of any (X)HTML spec, its obsolete. But you will soon be able to implement its behavior with CSS3: http://www.w3.org/TR/css3-marquee/
I find it interesting how you discuss the label in #6 and then fail to use it in #7 with the labels for the checkboxes – something that any form designer would do automatically (as Martin mentions below).
This article is enlightening to some, but I think it needed more proofreading before it was published. “rel” is also a very commonly used in microformats. I always use labels, and nearly always use fieldset, though for while I was incorrectly placing it on the outside of the form instead of the inside. That really messes things up when validating to XHTML strict.
Quite a few of these aren’t rare at all. fieldset, legend, label are all pretty much mandatory, in some cases because of the doctype, in pretty much all cases because it makes your forms much better.
To be really honest, the only truly rare tag in this post would be the WBR tag. That one really is hardly ever used. The others are IMHO common. Possibly not as common as a P tag or a DIV tag but still… rather common.
It’s interesting how the address tag has changed to a different use due to misuse. Originally it wasn’t intended for displaying a location address, it was for addressing the author of a document. It looks like the W3C Schools now supports your use of the tag.
Label isn’t really that rare. In fact, it’s essential for blind users who use a screenreader. Without it, form elements have no context. If you’re not using it, you really shouldn’t be calling yourself a web developer.
The ‘address’ tag is not for marking up general postal addresses. It is for supplying contact details of the author of the document. If you wish to semantically mark-up a postal address, use Microformats.
I don’t make a habit of slagging off blog articles but this is poor and a great example of one or two good points diluted by filler to ‘make up the numbers’…
It seems as if the author run out of ideas and has had to resort to including an attribute (rel is not a tag) and ‘wbr’ as a tag i really should know? Come on… Readers might like to know that wbr isn’t and never was part of the HTML spec.
It is widely recognised that there is no need for both the ‘abbr’ and ‘acronym’ tag and as such, there is no acronym tag in the working spec for HTML5. Yet the author appears to be encouraging the use of both?
I was glad to see the ‘address’ tag until I saw the explanation to why one would want to use it. The explanation is misinformed, that was not the intended use.
Anyone who wants to gain a better, TRUE understanding of HTML elements should go to the W3C spec and read the guidelines.
Just wanted to write the same.
This article is a mess. I thought someone keeps an eye on what is being posted here.
Sorry to say that but the author simply does not understand the meaning of some HTML tags. And you can just have a look at the comments to see how many begginers are going to use those tags the wrong way.
Regarding abbr and acronym, I would disagree. Semantically, they’re not the same, so they, in my opinion, each deserve to exist and can be used appropriately.
I was aluding to this when I posted my ’similar to the sitepoint’ comment. A post’s worth isn’t proportional to the amount of time spent writing it, but I can’t imagine that this took long to knock up. Still – it’s got people talking – is that not the purpose of a blog?
A ‘tag’ is the word in angled brackets that comes at the beginning and end of an element. An ‘attribute’ is something added to the tag which further describes the element.
This post has mixed up the use of tag and attribute and doesn’t explain elements at all.
For beginners this will perpetuate the confusion and simply annoy anyone who understands the difference and how to properly use the elements described within.
Nice List.
I think you dropped some text in number 10 – something between ‘try’ and ‘or’?
“If you were wanting to achieve the same effect but without using the tag, you could also try or should be noted that none of these tags have full support across all browsers.”
Decent write up and Ii picked a few things up, however I ought to point out that ‘address’ should only be used to ’specify such information as address, signature and authorship for the current document’ (from w3c html3 spec) it is not an address element for listing a number of offices in an organisation for example. For addresses you are much better off making use of the vcard microformat.
Also I would advise against using acronym at all as it is dropped from the proposed html5 and xhtml2 specs as it was deemed that abbr is more semantic.
A good use for the rel attribute is for microformats as well including xfn which helps you to specify yourself at different urls (e.g. homepage, twitter, flickr etc)
Due to the amount of forms I create, fieldset and label are second nature to me, and rel is used in a number of lightbox implementations which is where I first came to grips with it.
I can see real uses for cite, optgroup, address and abbr, but I think the remaining tags, although useful in their own right, would only be applicable in a tiny number of cases, and wouldn’t class them as ‘must know’.
But saying that, I bet I’ll use them in the future now I know them! Great article to bring some little know tags to light.
I’m amazed to see some of these tags here as many are certainly not rare (and not all are tags anyway).
There’s also a few mistakes.
wbr is not part of either the HTML or XHTML specification, even though some browsers recognise it. It was designed to provide browsers with an optional place to break text within a nobr tag, so should always be used within a nobr tag (if you want to use invalid code).
A better example of acronym would be acronym title=”cascading style sheets” CSS. Your example is completely wrong.
The example for cite is misleading. A better example would be, for eg.
blockquote: paragraph from, say Wikipedia
cite: attribution to the source
(You will have to imagine the code since I cannot format here in the comments).
I wouldn’t recommend that anyone use this tutorial as a guide but if any of the tags or the rel attribute are new to you, look them up on the W3C site. There’s not much point in using new code if you don’t use it correctly!
What? Wrong. Rel is used all over the place. It is used often to assign events in JavaScript to anchors with a given rel value. Ins and Del are used often as well. A lot of WYSIWYG editors use this when you do inserted strings or deleted strings (like in TinyMCE). And a decent amount of people use cite rather than blockquote.
And label? Lots of people use labels within forms.
Great article! I’ve been using ‘abbr’ instead of ‘acronym’ in my sites and will definitely revise them to reflect this more semantic mark-up. Thanks for the tip!
Yeah the address tag was never intended for marking up an address. I would always normally use it for a contact email address or similiar, basically contact details. Then use VCard Microformats to mark up an address.
You should make a note that ACRONYM is deprecated in XHTML in favour of ABBR as ABBR covers both acronyms and abbreviations semantically speaking. ADDRESS is not for location either as others have stated, HTML5 aims to deal with poorly named tags like this however.
Honestly, any decent HTML coder/producer not knowing and not using fieldset, label & legend when coding a form cannot pretend to be a pro-coder.
Those tags must be used when producing a form : basic accessibility.
As for rel, it is not a tag it is an attribute.
I agree it can be used with js a expained here but it is absolutely not the original pupose of this attribute.
Any of those tags, optgroup, cite…. are not obscure at all. They just have one very spcefic purpose and they cannot be used or tricked into becoming anything else. Any pro-coder know those tags !
May be wbr is obscur indeed… So obscur that W3C does not know this tag!
Since I started using CSS I avoid these tags completely. If I want an address to look a certain way, I just make an address class in my stylesheet. Same for Blockquote, Cite, etc. My own class names are usually easier to remember than old html 1 tags.
THe problem is that if I leave it up to the browser, and each browser interprets these tags differently, than I have to take complete control anyways. Might as well make them classes.
(though I must admit though that “acronym” would be useful)
From an accessibility perspective, it drives me nuts when label tags are not used. While you can select the corresponding input field by clicking on the text, labels also give those input fields real names that are read aloud when using a screen reader. (Rather than just “Input Blank” it would read “Input Username,” or something along those lines.)
As web designers, a main focus should be accessibility.
For , I’ve been using microformats, and I didn’t even know , , or existed! – although I have been using for and I think the underline from may be confused with a decorated link tag.
And 1 more thing, if u call yourself a webdesigner and never heard of this tags then i don’t know what to say.
6 out of 10 are used in almost every work
The address tag is not only for addresses. It is meant to display the page author or owner’s contact information, whether that includes name, phone number, email address, physicall address, etc.
And yeah, labels and fieldsets are essential for building forms properly, I don’t care what doctype you’re using.
Yeah I don’t think labels and fieldsets are “rare”. Every developer who works with forms at all use these, or at least those that care about accessibility and web standards.
“The address element isn’t used for the purpose that you may expect—that being to mark up a physical location alone. Instead, it’s used to indicate the contact point for the document in which it appears. This element would usually appear in a header or footer on the page.” Sitepoint html reference
I’ve come across most of these before but theres a few little odd ones including the . I don’t think I would leave it up to my browser to decide on the page breaks!
But I used acronym here! Lawrence77 Most of the wordpress comments supports this!
its not a rare then!
But all the others are very cool!
thanks for sharing!
They’re “elements” not “tags”. And in the example not applying a element to text adjacent to a radio button input allows both radio buttons to be selected. By using with the matching name to the you can assure only one radio button can be selected, and the label itself is clickable.
Doesn’t ‘rare’ imply collectibility? It’s kind of difficult to collect intangibles like, well, HTML tags. I think the word you’re looking for is ‘obscure’.
I’ll leave you alone about how you actually used said tags; everyone above me has tore into you enough as it is.
All in all, a disappointing article from NetTuts; it’s like the site is losing its touch. It’d be understandable if this were written by some guest columnist type, but Glenn is a regular contributor here. That’s too bad, I guess one can’t stay at the top forever. Or even readable.
no they’re not. and no, i won’t. i disabled adblock on this page. that is good enough.
Doug March 24th
Lowell,
Rare does not imply collectors item. Rare implies “not often found”. Collectors items are usually rare, but so are beautiful women, smart presidents, and guys named lowell who aren’t douche bags.
Just a few comments:
– I sat in on an accessibility lecture not too long ago and they really ripped using “optgroup”, turns out it’s very confusing to a screenreader.
- acronym is being dropped because of the cloudy definition and overlap with abbr. So we’re using abbr now (personally, I like using acronym over abbr, when there’s gray area).
- while “rel” is a great attribute. Using it to define a clickable region is a bit of a stretch. The AIRA spec now takes care of defining roles for accessibility: http://www.w3.org/WAI/intro/aria (should be finalized soon)
- for “wbr”, there’s a cool css3 property coming out for creating word-breaks, very cool. I’m looking forward to using it.
I think that’s all, good list though, I’ve never used “ins” or “del” before, very cool for editing!
is a possibiliy to tell the browser to make a line break here if necessary. I use it often in German language with words combined by “-”, because not all browsers brake these combined words: “Print-tastic” -> “Print-tastic”
To “syllabicate” large German words, I use “”, which is unfortunately not interpreted by every browser.
The wbr tag really contradicts the semantic approach to HTML, so I would personally avoid using it, in favor of appropriate UTF characters. The rest are useful though, and I seriously doubt anyone has failed to notice the label element.
Additionally, with regards to “rel”, if the argument is for working with JavaScript, use a class or an id instead because rel is not supported by all browsers. for example, <a class=”clickable”> would be better than <a rel=”clickable”>
Great article, Glen! Interesting how many people talk about the semantic web but noone is currently using existing tags that makes the code more semantic.
I use on the contact page, and whenever I make an explanation or a definition of an expression someone maybe is looking for, I use the -tag.
The and is a very good SEO-tool, because you have USA and United States of America at the same time in the text whithout bothering people with repetition, and the search engine knows that you are really talking about the United States and not about another kind of USA like the Unbelieveable Sucker Association.
Taking a look at the next generation tags of xhtml I really wondered that these guys didn’t take the chance to create a bunch of semantic tags that enables a machine to discover what a text really contains. Examples:
(image with content) vs. (functional image) vs
(outstanding content that appears on every page and should not be considered to be part of the content)
(visible label line under an image)
(in a new semantic way)
Incredibly misused tags. They’re for definition lists but somehow designers always seem work them into sidebar columns and people like me always seem to work them into regular inline HTML (body copy) for tutorials and the like. I wish there was an equivalent that was also semantic and offered as much flexibility.
I think people are frustrated because this site is frequented by beginners: i.e. people that will be our colleagues and employees in the future. So let me state the things that I feel should either be corrected or removed:
1. Labels and fieldsets are not rare at all. It’s part of web form best practices. It is part of giving your web forms a good structure. Unless you learned web design/development purely from W3CSchools, labels and fieldsets are not rare or obscure at all. Most web developers who actually do web development know this already and to say “one of the most forgotten” implies that it’s rarely used and therefore isn’t important, which it is if you care about a semantic structure and better accessibility. A more obscure ‘tag’ in my experience from working with developers of all levels are <pre> and <code> – it’s a favorite interview question of mine to gauge their knowledge of HTML.
2. the rel example is just not good. I say this because that is poor use of the rel tag. Based on the argument used, it should be a class and ID. Using rel also invalidates your code so if you care about standards set by W3C, avoid this attribute at all cost.
3. rel example again: “and it knows to apply some Ajax“… um… wtf. What does that even mean?
4. The example used in the rel attribute example is NOT “one of many techniques you can use”, you shouldn’t use rel for the example you used – the right way would be through a class or ID for that example.
5. <wb /> should be used in the example, not <wb> if you absolutely must use it. Note that in the reference you used, in the footer section of Quirksmode it says “this page is not valid and is for testing purposes only”
6. In number 10, Should really change <span> to <p> because (a) you should never have a span tag that isn’t enclosed in another element, (b) it would be semantic to do so.
7. If you insist on calling it tags, then there are only 9 ‘html tags’ on here because rel is an attribute of an ‘html tag’.
I hope you truly consider revising some of the errors on this article because new and young developers will be reading this – it’s a big responsibility to make sure that you always share best practices and promote web standards, for the sake of those of us who have to work with the new guys.
First, I will tell you this pretty straight: You’re the worst writer from Nettuts from my point of view. Considering the comments, others may share my thought.
All other tutorials offer valuable information while yours show 10 “things” all the time. No offense but if you not technical enough and can’t create a important and valuable information – that’s OK. All you have to do is research and find out. But try and verify your content before sending it to the community.
PS: Thank you guys for this valuable comments. This is a real community.
But take a look at those newbies that are saying what great tips they found in this article. That is what you should be afraid of. Many new designers wannabes will take this info for granted – this thought gives me the creeps.
mbarvian March 24th
Wow, I haven’t seen many of these. Thanks for posting!
I don’t see how a person can call themselves a “web developer” when they have very little understanding of the most basic thing about web development: HTML. Why didn’t you use a labels for yes and no in the fieldset example? Have you worked with forms before, because if you have, how can you say label and fieldset are rare? If the answer is yes to my question and you have worked with forms before, that’s just sad.
is not a valid html 4.01 or xhtml 1 tag. The wbr-element is not part of w3c’s HTML spec at all. That’s the reason the tag is little known or used. My advice would be to stick to standards.
I just want to say I use the wbr tag in my site, and I am happy with it. I have a script that inserts it every 20th character in long unbroken strings of characters, to allow them to break. These are usually long URL’s that are being printed on the page, and so nice wrapping is very helpful.
Also, my script instead uses if on Safari (since safari doesn’t support wbr), and does almost the same thing, but with a printable hyphen at the break point. The combination of the two covers all major browsers and provides nice wrapping.
Standards be darned, there are uses for things like this. And it seems to be well supported at the moment.
Some of these tags are incredibly useful for making use of semantic markup. It always makes sense to use the tag which best describes the content. Tags like and do just that.
This article is disgraceful to both newbies who are using it to learn from and REAL professionals who know better.
You know what else is a rare tag? . Double points if you nest it in a . Triple points if you use comic sans and apply it using the tag
The sad part is my sarcastic example is every bit as valid as your example of the REL attribute. If you are going to use it for “AJAX” you’re better off just make up a attribute such as anotherNonValidJunkAttribute=”clickable” because they can be targeted the same in JavaScript but in my example Google won’t read the REL and think that the link is related to “clickable”
In these Web 2 days, label and fieldset are pretty commonly used for designing forms; and rel is of course used everywhere. So at least these three are not “rare”. optgroup is also pretty common, though it is starting to become less common now a days mostly because select boxes are being replaced by custom lists.
Man, these tags are awesome. Its really helpful for Webmasters, I will use them in my Websites. Specially the Acronym Tag, its really good and worth using.
If you’re going to abuse semantics instead of using acronym for definitions why not use abbr it’s shorter and there’s at least some rationale behind something like
[abbr title="twitter: a microblogging website"]twitter[/]
Whilst there’s no way “twitter” is an acronym. I just use a span with a class=”defn” attribute and a title then style it to match the acronym and abbr tags. Works the same way then and is more correct.
I dunno, it just seems like if it’s outside the realm of a CMS, a Bullet Proof Web Design book or AJAX it’s treated as some lost art. Kinda sad really, seeing self proclaimed developers thinking simple HTML or XHTML tags are forgotten or rarely used.
It’s a decent article with some strange examples to support the points made, but over all it went well with the time I had to kill.
I hazard a guess that would stand for “wrapping break”, meaning that the break would occur if the line of text had to be wrapped inside a container or table cell or something. That would be useful today, I can’t stand seeing the amount of widowed and orphaned text on web pages in general.
Anyway, like 1000+ people have said before me, there’s a good reason why alot of these tags are not in use. They’re replaced with better solutions, or CSS. God help you if you use or , or or for that matter.
In response to all the complainers… You can never make all the geeks happy. I think the post is great and I appreciate the effort to put this list together.
they are not really rare and they are used on pages where appropriate. i’ve seen them a lot on bibliographies, thesis, survey forms, etc. i agree with you on . it is hardly ever used.
Nice list. I would say that the rel attribute isn’t really all that rare. It’s starting to show up a lot for various JavaScript/AJAX and SEO tricks.
Your list is missing a set of tags that are rare in my opinion: DL, DD, and DT. The definition tags are rarely seen, but can be quite useful for term definitions or even FAQ pages.
I can only re-iterate what has already been said in the previous comments. Yet another woefully inaccurate article from Mr Stansberry. Here’s to future Nettuts+ articles being much more on-target and faithful to their titles!
More bugs: Your radio buttons are not linked so you can select all of them at once and on FF3 the fieldset does not draw a box around the fields. (At least, it doesn’t in your example.)
“rel” seems out of place in a list of html tags but, as you said, it can be very useful and seeing it on anything other than link or anchor tags is quite rare.
Don’t forget when making AJAXy things that not every uses javascript. Make sure your links and buttons still work with javascript turned off. Especially in the case of links, this will help your Google ranking as well as not turning away visitors who don’t have javascript turned on. (Like me)
For instance, there are no labels on this comment form. They are placed inline using javascript after the page loads. I can either guess that they are in Name, email, URL format as most blogs use or I can look at the source code and hope that the names are descriptive. For some reason you have used the attribute “defaultvalue” in these input fields which does not exist rather than the more standard “value”… which would have worked. Using a label would have been a much better idea.
I think it would be a better use of your time to run your pages through the W3C validator than to start learning obscure and badly supported tags that add very little benefit to the average user.
What’s most sad isn’t the fact that this Jesus-esque character “Glen Stansberry” made money on writing this “fine” piece of … article, but that more feeble minded developers are taking these “tips” at face-value, quite possibly applying them in their work. Here’s what I have to say: read the first 20 comments and learn the real deal.
The wbr-tag you say? Why not also enlighten us on the usage of the marquee-tag and the blink-tag too? Haven’t seen those around lately.
Jesus…you guys are such nit-picky bastards. Does anyone actually code or do you spend every ounce of your time picking through simple tutorials and arguing with each other over correct semantics…and spelling in each others comments. For christ sakes…i could only read like the first 15 comments before i confirmed that i was wasting my time. And yeah, i prolly spelled something wrong.
It’s not an abbreviation. If you try to teach someone how to spell the word “bark” and they spell it “barc” they would need to be corrected. Sure it “sounds” the same, but it’s not the right way to spell it. When what you’re doing is educating others, you need to be precise with what you say and teach.
Just another comment to read. Everything has been beaten to death in one direction or the other and I wanted to do something telling myself reading all of this was not a total waste of time. Cheers!
i can’t quite believe I didn’t know some of those tags. What particularly surprised me is the existence of the optgroup tag. It also seems to work cross-browser.
What has happened to the TUTS? There’s an awful lot of sales-pitch lists and poor/under researched content… Why would I consider paying for the TUTS+ stuff if this is the quality diplayed?
Sorry to tbe the fly in the ointment but you really are missing some important stuff here and its quite typical of the semantically challenged.
1) acronym is not for adding info about something, if you want to do that use a span. It’s a *specific* form of abbreviation NOT expansion. YMCA, FBI etc are acronyms.
2) abbr – even though this is a great tag (even though ppl use acronym instead wrongly) it’s not supported by ie6/7 [and probably 8] so nothing will show up if you use it.
Was hoping for an informed article but this fails, epically.
Nice list. However, your fieldset example doesn’t work. You need to have the name attribute be the same. Since your example uses different names, they will both be selected instead of one OR the other.
Your definition of the tag is wrong : you say it «defines a group of words» but, as its name says, it actually defines an acronym… «Twitter» isn’t an acronym, «SEO» is.
Yeah, I really don’t use those HTML tags at all. I’m trying to figure out how to get a list arrow for my css navigation pane. Anyone’s input would be greatly appreciated.
I was prepared to reply after the first half of tags and brag that I got to use them all. But I have to admit, the last one: wbr is the one I didn’t use.
btw I think wbr is no longer supported in ie8. Microsoft just wants to be special.
Create Christmas Designs With These 50 Sets Of Pho Give your Christmas designs this holiday season a personal touch by creating your own designs. Here are 50 sets of quality Photoshop brushes for your projects.
Web Design Harmony: Concept, Conveyance And Theme Concept is what you want to communicate. Conveyance is how you will communicate it. Theme is how well you coordinate it. This post will help you with some higher level thoughts and ideas behind designing a website.
18 Impressive Web Form Validation Scripts To Enhan Forms are such a common element on the Internet we tend to blunder through them without too much thought. However, if the web site has added a few nice touches that make the process easier, it tends to speed up the process and reduce any frustration
200+ Javascript / JQuery Tutorials For Designing A In this list I have included some great tutorials on jQuery and Javascript. Jquery & Javascripts are used for making the websites for attractive and usable.
10 Javascript & CSS TreeView And Sitemap Plugins A Javascript Tree view and sitemap are good tools to display the structure of your website. I have collected 10 plugins and tutorials that will save your time hunting for one.
Site-Specific Browsers: Turn Sites To Desktop Apps As web designers/developers, desktop applications are harder to create as they have a totally different environment.
We can make use of site-specific browsers which enable us to lock a website inside an application-looking browser.
Over 38 Free Flash Photo Gallery Ready To Use For Flash galleries are getting more and more popular these days. If you’re going to give a professional look to your image gallery, this post is your chance to check out over 38 professional ones.
Free For All: Winter Holidays Edition Whatever winter event you're designing for, you'll want these free fonts, clip art, stock photos, and WordPress and Blogger templates.
User Comments
( ADD YOURS )darklord March 23rd
Woooow i’m the first one unbelievable ,
( )nice tuts by the way some of those tags i see them for the first time in this tut.
does anyone knows if this site is going to post any .net tut ??
lawrence77 March 24th
what is special in ”10” Mr.Glen Stansberry
Out of your 25 tutorials in PSDTUTS u wrote 20 in the starts with 10!
Anyway all ur tuts/articles are fine!
( )I except Ajax+c#.net+Asp.net from you!
thanks!
Lawrence.J
nixxy March 25th
.net is gross
( )Valamas March 25th
.net is grouse
Lawrence77 March 25th
no its elegant!
kw March 28th
you probably know nothing about .net.
Erwin July 4th
.net is great.
I program (my job not a hobby) in Java and in c#.net. If i would have to choose between the two then .net would definatly win.
Mike September 16th
.Net sucks +1
Devin March 23rd
rel is not rearly used
( )Sebastian March 23rd
Have to agree with you there…
( )I have almost never seen a site without <link rel=”stylesheet” ………..
aljuk March 24th
“Rearly”?
I use rel on every site I build, as in rel=”ext” to define a link as being to an external website. Javascript picks this up and opens the link in a new window (rather than using target=”_blank” which is depricated in Strict).
Back to web design “skool” for you I guess…
( )Jonny Haynes March 24th
Or maybe back to the web design school for you.
Good usability and accessibility practices show that you should never force the user to open a new tab/window. V bad.
Leave it to the user to decide themselves.
Jake Boxer March 24th
@Jonny Haynes
This is true most of the time, but there are plenty of occasions where you definitely want to force the user to open a new tab/window.
The most common one is when you have a site targeted at less computer-savvy users and you have a link that, if opened in the same window, would interrupt a set of steps they’re going through.
For example, I maintain a website where people can post and search for apartments (much like Craigslist). The apartment posting process has 7 steps, each on its own page. Many elderly folks with extra rooms in their house post apartments here, and many of them aren’t great with computers, so on each page, we have a link to a video tutorial that explains how to fill out the current page.
If a user clicked the video tutorial link on step 4 of 7, and it opened in the same page, they would need to navigate back to their half-complete listing after watching the tutorial. While this would obviously be no problem for you or me, it can be very confusing for someone who is unfamiliar with computers.
Instead, we open the video in a new window, and include text saying “When you’re done watching this tutorial, close this window to return to your listing.” If we didn’t force open a new window, many non-computer-savvy users (the very people we’re trying to help with usability/accessibility practices in the first place) would end up much more confused than they do now.
Jonah March 24th
“depricated”?
Jonny Haynes March 25th
Why not just use something like ‘Lightbox’ or ‘Highslide’ (with a non-javascript fall back) with an iframe inside it? That way, they never have to leave your site.
We’ve done that on numerous occasions for things you’ve already mentioned.
Joe Wiggles March 25th
I work at a newspaper site and we always use “target=”_new” for our advertisements. We’ve found that many times when a user clicks off of our site to another they will lose track of where they were originally and go on to other things. Our strategy is to keep our site in the background or on another tab so that hopefully when the user closes this new window, our site will still be easily available. No complaints so far.
Whatever April 8th
Oh wow, you complain about spelling.
How very nice of you.
Thumbs down.
r953 March 25th
rel is an attribute not a tag…
( )Tokyoish March 25th
anyway, “rel” is not tag. It’s attribute.
( )Louis March 23rd
Informative post, however wouldn’t it be more appropriate if the examples were in XHTML? I don’t think anyone that codes uppercase HTML without quotes around attributes is going to use any of these tags.
( )Snookerman March 24th
Why XHTML? IE doesn’t support XHTML.
( )Meshach March 24th
What are you talking about? IE does support XHTML.
william March 24th
IE DOES SUPPORT XHTML if the XHTML is CODED in HTML COMPATIBLE MODE and you use the right DTS example
Why?, because it will be close to the new standards, and xhtml is an step in the right direction you will have the content easier to update and migrate
Dan March 24th
IE doesn’t support the internet.
Snookerman March 24th
IE doesn’t support XHTML (not even IE8) so what you do is pass the XHTML code as HTML (http://www.w3.org/TR/xhtml-media-types/#text-html) and all browsers will parse the page as invalid HTML with a bunch of unnecessary forward slashes and unclosed tags, a so called “tag soup”. XHTML is good, but only if you use it in the right way with the mediatype “application/xhtml+xml” (http://www.w3.org/TR/xhtml-media-types/#application-xhtml-xml) in which case IE users will now see the page but will be asked to download it. The best solution at the moment is to use HTML4strict. Nobody stops you from using lowercase tags and quotes around attributes, it’s actually good practice (http://www.webdevout.net/test?html4-good-practice).
If you want to learn more, read this article:
http://www.webdevout.net/articles/beware-of-xhtml
It’s long, but it’s worth the time since most people don’t really understand what doctype they are using.
Jonny Haynes March 25th
@Dan
“IE doesn’t support the internet.”
Genius, I’m going to use that today in a meeting! ha ha!
Oscar March 25th
@Dan
“IE doesn’t support the internet.”
Love it
( )Evie April 7th
@Dan
“IE doesn’t support the internet.” —
One of those jokes I’d love to be able to drop into a conversation somewhere, but really couldn’t without seeming like a complete geek
Ethan March 23rd
Very cool! Haven’t heard of half of these.
( )Joost March 23rd
I thought fieldset is required for forms when using the xhtml strict doctype? It should be in your forms if you use xhtml.
Actually, I always use fieldset, legend and labels for my forms.
And another one cool (rare?) tag I love for forms is button instead of input type=”submit”. It’s so much easier to style with css and allows icons in the buttons. It validates, and I have yet to find problems with it. But w3c doesn’t recommend using it.
Didn’t know about optgroup and wbr though, thanks!
( )Chris Simpson March 24th
I agree that the button tag is great, and especially to style, the trouble is that different browsers (IE grrrr) interpret it differently if its placed in an HTML form.
( )Chris Robinson March 24th
you’re correct if you want your XHTML 1.0 Strict to validate you have to use fieldset with your forms
( )Andy March 25th
is mostly fine, until you have a form with multiple submit buttons.
( )IE6 only recognises the value of the last submit button in your form.
So, if you have a Save button, followed by a Cancel button, all buttons will take on the value of Cancel.
sam March 25th
kind of off topic, but im surprised that nettuts itself doesnt validate.
( )Angel March 23rd
very very cool!
( )Paul Armstrong March 23rd
It’s most unfortunate that you mis-used half of the items in this post.
cite should be used when you’re actually _citing_ something from a source, like if you’re using a blockquote or q element.
optgroup should contain a set of options, not be closed before the options. Your “live demo” doesn’t show any visual difference because of your improper usage.
acronym is used for acronyms. Defining acronym, “a word formed from the initial letters of the several words in the name”… The usage in your example just hurts my brain.
According the HTML specs, address is used to denote the address of the page creator: “The ADDRESS element may be used by authors to supply contact information for a document or a major part of a document such as a form. This element often appears at the beginning or end of a document.” See: http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.6
Pretty sad that you didn’t use labels in your fieldset example.
The abbr example is a better example of an acronym. abbr, or Abbreviation is a “shortened form of a word” like ‘management’ -> ‘mgmt’.
rel should be used to describe the relationship of the text to the current tag. W3C says, “This attribute describes the relationship from the current document to the anchor specified by the href attribute. The value of this attribute is a space-separated list of link types.”
wbr is not in any HTML spec. It is a non-standard tag that was added by Netscape, and later dropped around Netscape 4 or 5.
I’m incredibly disappointed by the inaccuracies that you’re giving people who might not know better.
( )Kenneth March 24th
I was just about to make all the same points.
( )Newton March 24th
seriously, way to go and set web development back to the 90s with this tutorial. I’m kind of appalled at Net Tuts for allowing this content to go up. Makes me wonder what other crap they’ve let slip through their hands.
( )Snookerman March 24th
Thanks, you have saved me a lot of typing, I was just about to start writing why my brain melted while trying to go through this article.
The only thing I would add is that rel is not a tag.
I think it’s really weird that nettuts accepts articles like this one which was obviously just written for money, not for teaching people. Shame on you glen.
( )Will March 24th
I concur.
Glen’s articles are unfortunately usually of poor quality. I tend to browse through the comments to find there is always someone like Paul serving out cold hard facts.
Anonymous March 24th
Thank you for posting the clarifying information. I can’t find anything to confirm that “rel” is a valid attribute on ALL html elements. I only see it applied to A elements.
( )Anonymous March 28th
It is also valid in LINK elements.
Sean McArthur March 24th
You mostly corrected everything I would have.
But c’mon, your example of what a real abbr is (management => mgmt) is exactly how he used it! Sergeant => Sgt. His use of the abbr tag works just fine.
But the acronym usage (Twitter??) is totally wrong. It only would have been correct if Twitter stood for something.
It appears though, that acronym and abbr were listed for the effect of providing a title on hover… A title on any element at all will provide the hover tool tip. A better use for the Twitter case would be <span title=”Found in 2006″>Twitter
( )Paul Armstrong March 24th
Sean: The article was corrected for abbreviation and optgroup after my comment was made.
I really try not to be harsh when dishing out the facts, but I expected a little error checking by a professional before something like this would be posted.
Marah Marie March 24th
Agreed on author’s unneeded mention of wbr. It’s messing up pages on one blog of mine big-time because it’s automatically inserted by the CMS (there is no end-user control over it unless I go and rewrite some Perl just to make myself happy). It’s inserted to break up long URLs and it does NOT validate as XHTML Transitional, so I imagine it doesn’t validate in Strict, either. My frustration with it is endless.
( )B Shelton March 25th
The radio tags in example 7 are not coded correctly; they should have the same name so that only ONE option at a time can be selected.
Furthermore, the FIELDSET example does not show a border (like it may by default) because there is a CSS reset on this page (e.g. borders are set to 0).
( )Harlan Lewis March 25th
Agreed. Honestly, this article should be pulled or significantly edited – right now it’s simply too inaccurate to be of use.
And on WBR, as Paul mentioned it’s a non-standard, deprecated tag (so shouldn’t be in this list at all), but on top of that it’s used wrong – WBR would only go inside a NOBR tag, which is deprecated as well (replaced by CSS whitespace: nowrap).
Points for encouraging use of things like ABBR, but mistakes are just stacked on mistakes in this article.
( )Harlan Lewis March 25th
er… white-space: nowrap
just an example of when something needs to be edited…
Luuk Lamers August 23rd
Usage instead of wbr could be the validating and which almost do the same and wouldn’t need to be inside a NOBR tag or any tag at all. it’s just a break-up technique.
Luuk Lamers August 23rd
Sigh, shitty site for not using htmlentities().
I wanted to say:
Usage instead of wbr could be the validating [&]shy; and [&]#8203; which almost do the same and wouldn’t need to be inside a NOBR tag or any tag at all. it’s just a break-up technique. delete the [ and ] signs from the content above to actually have it working.
scott kimler March 26th
Paul … Agreed. ’bout blew my lid when I saw the semantic abuse of <acronym>. I use <span class=”info” title=” More information here “> for stuff like that. Plus, I’ve even made a pure-CSS popInfo box, if you’ve more information than what might show in bubble-text.
http://randsco.com/index.php/2007/12/22/rockin_da_sidebah
This article should be stricken. (”rel” a tag? geez)
( )Cru March 27th
Ugh.. reading that critique turns my stomach for the thousands of ways every developer thinks their way is the right way until another claims they’re wrong. All the while, practically everyone’s work is breaking under some condition… never completely satisfying.
( )Oscar Godson March 23rd
Yeah, fieldset is required and if you are not using it then you aren’t even making forms the right way
If you haven’t used it, every site you have done should fail on validation, so hopefully this isn’t too rare…
( )Kitanya March 24th
Required with what version of XHTML? I have validated many pages with forms and never used a fieldset and they have all validated. I am using 1.0 Strict.
( )Oscar Godson April 1st
OK, let me explain myself further
Every needs to have some sort of block element wrapping the . You can not, for example, have but you _could_ have:
But this is not the _right_ way of doing this. When specifying a form you should put a WITH a , of course, because s need a block element wrapping them, like this:
Search
But just because you can validate a form by wrapping it with most all block elements(i *believe* can’t wrap it in a blockquote) doesn’t mean it’s right, for example, does this look right?
There are others you could do such as , but that makes no semantic sense. Even makes no sense really. I can understand and though…
Oscar Godson April 1st
Also, XHTML 1.0 is like saying “Hey browser look, it looks like XHTML, but it isnt! HA!”
XHTML really is just fad I have come to find out. I used to use XHTML, and still do where I have to, like WP, but it really is a fad. Unless you are using valid XHTML 1.1 (and declare XML), don’t use XHTML because it’s meaningless.
Oscar Godson April 1st
Damn it, netuts strips out code? Why not just convert it to html entities! It’s only 1 line of code!
Well, my previous comment now looks completely moronic, ok, to get to my point since I can’t actually show examples I guess, and there is no edit button, nor a preview button in site:
you can wrap you inputs in your form with MOST block elements such as p, pre, h1-h6, etc, but having
[h1][input][/h1] or [pre][input][/pre] makes no semantic sense and should not be done! Use
[form]
[fieldset]
[legend]Fieldset group name[/legend]…(inputs here)…
[/fieldset]
[form]
Liam March 24th
Except a site without a fieldset, will validate XHTML Strict.
( )lol March 23rd
chera meu cu
( )GF April 19th
Are you brazilian? You should spend your time writing good stuff.
( )Carl - Web Site Design Instructor March 23rd
Some nice stuff in here, I especially liked the tags , and .
For our development course the “rel” is very useful as its important to keep the Javascript outside of the HTML and the rel is that bridge
I will bring these into our course content for Web Courses Bangkok.
( )Tycho March 24th
Are you kidding? did you not real Pauls comments on all the fauls with this article. Following this will only lead your students to destruction. If you want to teach them proper web standards, send your students to http://www.w3schools.com not this article
( )Kevin Patrick Robbins March 23rd
Your use of the acronym tag is incorrect. It is not meant to define or further explain a group of words, but to provide the user with the ability to see the full name of an acronymic term, such as UNESCO, PETA or NCAA.
In fact, your example of the abbreviation tag should actually use the acronym tag, since NCAA is an acronym. Your description is correct, but the example is far from it.
Examples of abbreviations are:
ea (each)
( )tbsp (tablespoon)
km (kilometre)
abbr (abbreviation)
Stuart March 24th
If NCAA is an acronym, care to tell us how it is pronounced?
( )Dan March 24th
It’s pronounced en-see-aye-aye.
Dennis March 24th
LOL. An acronym cannot be pronounced, hence it’s an acronym! Acronyms are pronounced as individual letters. Kevin is right.
LOL is an acronym for laughing out loud.
jason March 24th
NCAA is pronounced as letters but not all acronyms are. NASA and SCUBA are two acronyms that have a proper pronunciation and are not just “Spelled” out. People outside of the USA may not know NCAA (which BTW can be pronounced “N-C-double A” as well)
jim March 24th
NCAA is an initialism. An acronym is pronounced as a word.
Alexander March 25th
“It’s pronounced en-see-aye-aye.”
I believe it’s more like en-see-eh-eh, with a Canadian Prairies accent.
Tzafra March 25th
Most people in the USA probably have no idea that SCUBA is actually an acronym. (Self Contained Underwater Breathing Apparatus).
Paul Armstrong March 23rd
Oscar Godson: fieldset is not required for all doctypes, only XHTML Strict
( )Louis March 24th
Actually, that’s not true. Fieldset is not required for XHTML strict. You can wrap your form elements in a simple DIV and it will validate just fine. As long as there is something in between the form and the field elements, it’s fine. For example, visit this page, which I coded a while back, and you’ll see that it validates for Strict but does not have a fieldset on either of the two forms:
http://www.foremostcanada.com/submitQuestion.php
( )Juarez P. A. Filho March 28th
That’s right Louis. fieldset is not required, but it’s semantically correct instead DIV tag
Oscar Godson April 1st
all of you, what ever happened to SEMANTICS! Yes, so does wrapping an input with h1 or pre, but no one would do that because, it’s not right, neither is wrapping your entire inner form with p tags or divs!
( )Brian K March 23rd
was new to me, thanks!
Oscar I really like what you have going on with your site!! Kudos
( )Aaron Boushley March 23rd
Apparently opt group doesn’t work in chrome… browsing in it right now and had to open up firefox to see the effect. Although it seems like a pretty nice thing.
And the rel attribute is valid on all tags? Thats nice.
( )Andrew March 24th
Worked in Chrome for me; great article, BTW!
( )Zachary Johnson March 23rd
No, Aaron, it was just used incorrectly in the tutorial. The optgroup’s should wrap the options.
( )Aaron Boushley March 24th
Ya… They must have fixed it… because it works great for me in chrome now. Had me a bit worried for a bit. Its a great article either way, just thought it was a cool tag, glad its not deprecated or anything.
( )Brandon March 23rd
The example you have for the abbr tag is actually an acronym and should have been used with the acronym tag.
I am a little uneasy about using acronym or abbr for anything other than what they are meant for. I worry about screen readers saying that Twitter is an acronym for “Founded in 2006″
I don’t think you are using REL properly either as REL and REV are both attributes of A and LINK and have specific uses. It seems with the example that you give that you might as well just use extra class names.
All the rest of the tags are good to use. wbr and label are both great tags.
( )Dinesh March 23rd
Good Contribution… Cool & neat. I need to have same thing for JS
( )Paulo Pereira March 23rd
Kinda disappointing that NetTuts, which usually has great quality posts, let this one slip with errors, such as:
( )* optgroup is badly used
* isn’t self closed ( is) and it isn’t standard. Using non-standard elements should be disencouraged.
Bruce Brownlee March 23rd
Yes, we often use the tag, often in combination with the and tags. OK, serioiusly, the acronym tag is handy, and the label tag is pretty useful if you do a lot of form work
( )Bruce Brownlee March 23rd
Before html got stripped, that said we use the wbr tag, often with the wtf and lol tags.
( )Merxhan March 23rd
Nice Article.
( )I didn’t know that exists. And is required when using strict xhtml.
XAngel March 23rd
Nice!
( )Tks a lot…
EVula March 23rd
Also note, it should probably be <wbr />.
( )Krunal Shah March 23rd
nice ones
( )art March 23rd
It could be cool if some of these tags were in WYSIWYG editors
Thanks for article!
( )Emily March 23rd
Nice article. The alternatives to wbr aren’t showing up properly in browser though, you might want to edit that.
( )Dave K March 23rd
NCAA is an acronym not an abbreviation
( )Jordan March 23rd
The use of the acronym tag is wrong. Twitter has no acronym so it wouldn’t require the use of the acronym tag. An acronym is: “A word formed from the initial parts of a name, such as NATO, from North Atlantic Treaty Organisation, or Commintern, from Communist International.”
Using “Founded in 2006″ is far from it!
( )Marissa Wells March 23rd
Beat me to it! Definitely incorrect usage. That seems like the sort of thing that could easily just be put in parenthesis or a footnote anyway.
( )insic March 23rd
? is this valid without a closing tag? I dont know this tag so maybe it could be like this
( )insic March 23rd
<wbr> ? is this valid without a closing tag? I dont know this tag so maybe it could be like this <wbr />
( )Marvin March 24th
‘wbr’ isnt part of the spec and therefore will invalidate your HTML regardless of closing tag.
Kevin Jensen March 24th
it doesn’t need a closing tag in HTML, but you could close it out with </wbr> or just <wbr />.
SelenIT July 7th
Validity of any markup means that it fits the corresponding DTD. No DTD for any version of (X)HTML contains the definition of . So is always invalid, with trailing slash or without it.
The requirement of closing empty tags with slashes is about XML wellformedness, not (X)HTML validity. XHTML pages must be well-formed to be parsed when served with proper content-type (e.g. application/xhtml+xml). In all other cases the well-formedness doesn’t matter at all.
EricTN March 23rd
w3c.org says this in HTML 4.1 discussing acronym and abbr:
Western languages make extensive use of acronyms such as “GmbH”, “NATO”, and “F.B.I.”, as well as abbreviations like “M.”, “Inc.”, “et al.”, “etc.”.
It appears the w3c would’ve wrapped NCAA in an acronym tag rather than an abbr tag.
However the word acronym is not clearly defined; some people believe it’s not an acronym unless you can pronounce it like a word (NATO).
None of the above necesarily means that the suggestions you made for the usage of the tags aren’t good ideas. Sometimes the tags don’t have the best names for what they are best used for.
( )Glen Stansberry March 23rd
Hey Guys, just a couple things about the article:
1. The example was messed up by Wordpress. We’re working on it.
2. The and examples are, well… wrong
I goofed on those. They should be fixed shortly to show correct examples of acronyms and abbreviations.
Thanks for reading, and keep up the great comments!
( )Glen Stansberry March 23rd
Er… ok and #2 in the above comment meant to say:
“2. The abbr and acronym examples are, well… wrong I goofed on those. They should be fixed shortly to show correct examples of acronyms and abbreviations.”
( )kirie March 23rd
talking about rare, how about this one
text here
I think only several people know this
I already know all 9 tag except wbr, and fieldset, label and legend isnt rare I think
( )kirie March 23rd
great my tag disapper
this is a rare tag that I was pointed
“marquee”
using to roll text or other element as long it was visible
( )Kitanya March 24th
The marquee tag is ‘rare’ because it is both invalid and not professional. I used it a few times while I was initially learning, but if you use it on a website be prepared for ridicule, haha.
( )Liam March 24th
Marquee is IE only, just like styling the scrollbars.
( )Angela Quattrano March 25th
Marquee works to some extent in Firefox and Opera. I wrote a very popular tutorial on using it. The target audience was of course people with middle-school taste in design.
Kev Jaques March 24th
There are easy ways to recreate this, simple bits of JavaScript will get the ball rolling again
As others have pointed out, fieldset, labels are required, not too many people look to WAI validation, going forward it’s going to matter.
( )Paperboy March 24th
I would love to see an marquee plugin for jQuery LOL!
Marah Marie March 24th
Marquee is a great tag. If you want to see it in action just read a lot of LJs and MySpaces where that and the blink tag still abound. Eventually you may get the notion it’s immature and unsightly but I liked it when I was just learning HTML.
( )SelenIT July 7th
MARQUEE tag is not a part of any (X)HTML spec, its obsolete. But you will soon be able to implement its behavior with CSS3: http://www.w3.org/TR/css3-marquee/
( )sky March 23rd
it’s so cool..
thank u for your post..
( )Mike Jones March 24th
Great post! Thanks for pulling some oldies but goodies out of the back of the tool shed.
( )Patrik March 24th
In the -section at #7, the radio buttons doesn’t have the same formname. They have yes/no now, which makes both of them clickable.
( )Andris March 24th
wanted to mention this, too. but you were first.
( )Phill Sparks March 24th
I find it interesting how you discuss the label in #6 and then fail to use it in #7 with the labels for the checkboxes – something that any form designer would do automatically (as Martin mentions below).
( )Lee Munroe March 24th
Never knew about a couple of these. Don’t know about the default styling of ‘ins’. Surely it deceivingly looks like a link.
( )Kenneth March 24th
No, it doesn’t (unless styled that way). By default, a link will be blue and an [ins] will be the same color as your text.
( )Christopher Murphy March 24th
Indeed does look deceptively like a link, but can be differentiated using CSS. (A point we make in our recent book.)
I find myself agreeing with a lot of the comments above, especially with regards to the fact that the word Twitter is not an . Ouch.
( )Jeremy March 24th
This article is enlightening to some, but I think it needed more proofreading before it was published. “rel” is also a very commonly used in microformats. I always use labels, and nearly always use fieldset, though for while I was incorrectly placing it on the outside of the form instead of the inside. That really messes things up when validating to XHTML strict.
( )Christopher Hennis March 24th
What is rare about these again? Are they collectible limited edition code snippets?
( )Antun March 24th
Really nice list. I haven’t heard for some of this tags although I’ve been playing with websites for the last 5 years
Hope to see more informative articles like this one!
( )Marco March 24th
Quite a few of these aren’t rare at all. fieldset, legend, label are all pretty much mandatory, in some cases because of the doctype, in pretty much all cases because it makes your forms much better.
To be really honest, the only truly rare tag in this post would be the WBR tag. That one really is hardly ever used. The others are IMHO common. Possibly not as common as a P tag or a DIV tag but still… rather common.
( )Mads Kjaer March 24th
The -tag is not used correctly. When marking up the meaning of the abbreviation SEO, you should use the appropriate -tag. Like this:
SEO
( )Mads Kjaer March 24th
Woops. Looks like the form accepted my -tag in my previous comment.
( )Ryan Roberts March 24th
It’s interesting how the address tag has changed to a different use due to misuse. Originally it wasn’t intended for displaying a location address, it was for addressing the author of a document. It looks like the W3C Schools now supports your use of the tag.
( )Marvin March 24th
Do yourself a favour and avoid W3C schools. Some of their examples are way way out of date and promote bad practice.
( )Stijn Vogels March 24th
Looks like does the same as
( )haRacz March 24th
In 6th u write about using label and in 7th when u can use it u don’t do it.
( )Pez March 24th
Label isn’t really that rare. In fact, it’s essential for blind users who use a screenreader. Without it, form elements have no context. If you’re not using it, you really shouldn’t be calling yourself a web developer.
( )Harley Alexander March 24th
Random.
( )Rob March 24th
Cracking article with some very useful tips.
Cheers
( )Koistya `Navin March 24th
Yeah, I have never seen that someone used tag. Let’s remove it from usefull tags list
( )Keith March 24th
The ‘address’ tag is not for marking up general postal addresses. It is for supplying contact details of the author of the document. If you wish to semantically mark-up a postal address, use Microformats.
( )Zwoep March 24th
You guys have used on your own site.
http://net.tutsplus.com/tutorials/javascript-ajax/build-a-top-panel-with-jquery/
( )Zwoep March 24th
suBi March 24th
and i thought i knew HTML
( )Poonam March 24th
Nice Post….New to many of them
( )Shane March 24th
Reminds me of the SitePoint article I read the other day.
( )choise March 24th
are these tags all valid in xtml-strict ?
( )duellsy March 24th
had completely forgotten about the wbr tag, could have saved some headaches not lot ago!
( )Darren McPherson March 24th
Heard of them all, used maybe half.
( )Marvin March 24th
I don’t make a habit of slagging off blog articles but this is poor and a great example of one or two good points diluted by filler to ‘make up the numbers’…
It seems as if the author run out of ideas and has had to resort to including an attribute (rel is not a tag) and ‘wbr’ as a tag i really should know? Come on… Readers might like to know that wbr isn’t and never was part of the HTML spec.
It is widely recognised that there is no need for both the ‘abbr’ and ‘acronym’ tag and as such, there is no acronym tag in the working spec for HTML5. Yet the author appears to be encouraging the use of both?
I was glad to see the ‘address’ tag until I saw the explanation to why one would want to use it. The explanation is misinformed, that was not the intended use.
Anyone who wants to gain a better, TRUE understanding of HTML elements should go to the W3C spec and read the guidelines.
( )Baa March 24th
Just wanted to write the same.
This article is a mess. I thought someone keeps an eye on what is being posted here.
Sorry to say that but the author simply does not understand the meaning of some HTML tags. And you can just have a look at the comments to see how many begginers are going to use those tags the wrong way.
Someone should correct all mistakes in this post.
( )Marc March 24th
Regarding abbr and acronym, I would disagree. Semantically, they’re not the same, so they, in my opinion, each deserve to exist and can be used appropriately.
( )Shane March 24th
I was aluding to this when I posted my ’similar to the sitepoint’ comment. A post’s worth isn’t proportional to the amount of time spent writing it, but I can’t imagine that this took long to knock up. Still – it’s got people talking – is that not the purpose of a blog?
( )Roy Tanck March 24th
How about the ruby tag? I didn’t know about that one until after I named my daughter Ruby
(Although it doesn’t really fall into the ‘you should know’ category)
( )Roy Tanck March 24th
Oh, and isn’t optgroup supposed to go around a set of options?
( )Tony Crockford March 24th
Grr, get the semantics right please!
A ‘tag’ is the word in angled brackets that comes at the beginning and end of an element. An ‘attribute’ is something added to the tag which further describes the element.
This post has mixed up the use of tag and attribute and doesn’t explain elements at all.
For beginners this will perpetuate the confusion and simply annoy anyone who understands the difference and how to properly use the elements described within.
( )Rob March 24th
Nice List.
I think you dropped some text in number 10 – something between ‘try’ and ‘or’?
“If you were wanting to achieve the same effect but without using the tag, you could also try or should be noted that none of these tags have full support across all browsers.”
( )Rich Clark March 24th
Decent write up and Ii picked a few things up, however I ought to point out that ‘address’ should only be used to ’specify such information as address, signature and authorship for the current document’ (from w3c html3 spec) it is not an address element for listing a number of offices in an organisation for example. For addresses you are much better off making use of the vcard microformat.
Also I would advise against using acronym at all as it is dropped from the proposed html5 and xhtml2 specs as it was deemed that abbr is more semantic.
A good use for the rel attribute is for microformats as well including xfn which helps you to specify yourself at different urls (e.g. homepage, twitter, flickr etc)
( )Martin Sarsini March 24th
Do you really consider fieldset and label rare HTML tags? If you work often with forms you can’t not know them, they are a MUST
( )Mike March 24th
Interesting if not entirely useful. Some I use, some I don’t and some I never will.
Rather than use surely these days it’s better to make a vcard.
( )Mike March 24th
[code][/code]
Boy! For a site about web site building you sure make it difficult to post code in the comments!
( )Mike March 24th
OK. I was talking about the “address” tag.
( )Westley Knight March 24th
Due to the amount of forms I create, fieldset and label are second nature to me, and rel is used in a number of lightbox implementations which is where I first came to grips with it.
I can see real uses for cite, optgroup, address and abbr, but I think the remaining tags, although useful in their own right, would only be applicable in a tiny number of cases, and wouldn’t class them as ‘must know’.
But saying that, I bet I’ll use them in the future now I know them! Great article to bring some little know tags to light.
( )Harsha M V March 24th
wow.
I have to try using few of them !!!
( )nishu March 24th
yawn list ! what about interesting tags like .. dt, dl, dd, dfn, kbd, legend, sub .. ?
( )Neil March 24th
and of course
( )Neil March 24th
sup
Scott Radcliff March 24th
Nice post. If some designers took note, they separate their content and presentation even further.
I agree with Martin Sarsini. Fieldset and label aren’t really rare HTML tags.
( )Elpie March 24th
I’m amazed to see some of these tags here as many are certainly not rare (and not all are tags anyway).
There’s also a few mistakes.
wbr is not part of either the HTML or XHTML specification, even though some browsers recognise it. It was designed to provide browsers with an optional place to break text within a nobr tag, so should always be used within a nobr tag (if you want to use invalid code).
A better example of acronym would be acronym title=”cascading style sheets” CSS. Your example is completely wrong.
The example for cite is misleading. A better example would be, for eg.
blockquote: paragraph from, say Wikipedia
cite: attribution to the source
(You will have to imagine the code since I cannot format here in the comments).
I wouldn’t recommend that anyone use this tutorial as a guide but if any of the tags or the rel attribute are new to you, look them up on the W3C site. There’s not much point in using new code if you don’t use it correctly!
( )Viorel March 24th
Hey, where are the labels from point 7?
( )dusoft March 24th
rel is not a tag, yes, you want to have a nice title, but you shouldn’t mislead beginners!
( )Timothy March 24th
What? Wrong. Rel is used all over the place. It is used often to assign events in JavaScript to anchors with a given rel value. Ins and Del are used often as well. A lot of WYSIWYG editors use this when you do inserted strings or deleted strings (like in TinyMCE). And a decent amount of people use cite rather than blockquote.
And label? Lots of people use labels within forms.
( )Mike March 24th
Great article! I’ve been using “” instead of “” in my sites and will definitely revise them to reflect this more semantic mark-up. Thanks for the tip!
( )Mike March 24th
Great article! I’ve been using ‘abbr’ instead of ‘acronym’ in my sites and will definitely revise them to reflect this more semantic mark-up. Thanks for the tip!
( )Rich Clark March 24th
Mike, see the above messages you SHOULDN’T be using acronym, abbr is just fine and acronym is due to be dropped in html5 and xhtml2.
Ollie Kavanagh March 24th
Yeah the address tag was never intended for marking up an address. I would always normally use it for a contact email address or similiar, basically contact details. Then use VCard Microformats to mark up an address.
( )Joe March 24th
Cool HTML tags ,but know most of them.
( )Nikhil - Powerusers March 24th
i have used some of them but the collection is superb……
( )Eric March 24th
I like the article. Funny, not too long ago I could have used that wbr tag! Next time, I’ll know. – Eric
( )girish [richi] March 24th
most of those wer already used and written by me in my articles.
( )Mark March 24th
Great info very useful. I like the INS / DEL, and I should have known about the OPTGROUP, will be using in the near future.
( )Freddie March 24th
This is a great article. Have added it to IHeartTopTens : http://www.ihearttoptens.com/view.php?uid=35
( )Wade Jackman March 24th
Great post, I forgot about some of those, and never heard of wbr.
( )Darren Paul Azzopardi March 24th
Hi Glen,
When did the tag become a way of marking up geographical locations?
Saying that I dont think it has too contain actual addresses…
The last time I read about this tag was when it was used to mark up contact information related to the document itself… :S
Oh boy, back to the reading board…
( )Robert O'Rourke March 24th
You should make a note that ACRONYM is deprecated in XHTML in favour of ABBR as ABBR covers both acronyms and abbreviations semantically speaking. ADDRESS is not for location either as others have stated, HTML5 aims to deal with poorly named tags like this however.
( )Mike March 24th
“rel” is not a “html tag” so you really only have 9 on the list.
( )Nick Tulett March 24th
Most underused tag for sites containing code samples?
samp
( )roni March 24th
Honestly, any decent HTML coder/producer not knowing and not using fieldset, label & legend when coding a form cannot pretend to be a pro-coder.
Those tags must be used when producing a form : basic accessibility.
As for rel, it is not a tag it is an attribute.
I agree it can be used with js a expained here but it is absolutely not the original pupose of this attribute.
Any of those tags, optgroup, cite…. are not obscure at all. They just have one very spcefic purpose and they cannot be used or tricked into becoming anything else. Any pro-coder know those tags !
May be wbr is obscur indeed… So obscur that W3C does not know this tag!
( )Jesel Morga March 24th
Cool post thanks for the article. a big help. ^_^
( )Joe March 24th
I hadn’t seen nor heard of WBR until a day or so ago when I was trying to get code for a constant contact signup form. They had it sprinkled within.
( )Daryl March 24th
Since I started using CSS I avoid these tags completely. If I want an address to look a certain way, I just make an address class in my stylesheet. Same for Blockquote, Cite, etc. My own class names are usually easier to remember than old html 1 tags.
THe problem is that if I leave it up to the browser, and each browser interprets these tags differently, than I have to take complete control anyways. Might as well make them classes.
(though I must admit though that “acronym” would be useful)
( )Damjan March 24th
You should read more about semantic code and SEO
( )Dan March 24th
CSS Reset will solve that, for the most part.
( )Sean Nelson March 24th
From an accessibility perspective, it drives me nuts when label tags are not used. While you can select the corresponding input field by clicking on the text, labels also give those input fields real names that are read aloud when using a screen reader. (Rather than just “Input Blank” it would read “Input Username,” or something along those lines.)
As web designers, a main focus should be accessibility.
( )BillyG March 24th
For , I’ve been using microformats, and I didn’t even know ,
, or existed! – although I have been usingforand I think the underline from may be confused with a decorated link tag.Thanks for the run down!
( )haRacz March 24th
And 1 more thing, if u call yourself a webdesigner and never heard of this tags then i don’t know what to say.
( )6 out of 10 are used in almost every work
Chris Wallace March 24th
The address tag is not only for addresses. It is meant to display the page author or owner’s contact information, whether that includes name, phone number, email address, physicall address, etc.
And yeah, labels and fieldsets are essential for building forms properly, I don’t care what doctype you’re using.
( )Jacob Gube March 24th
Yeah I don’t think labels and fieldsets are “rare”. Every developer who works with forms at all use these, or at least those that care about accessibility and web standards.
( )Arun J March 24th
This blog post has hit the twitter trending topics! Wow!
( )yannick March 24th
“The address element isn’t used for the purpose that you may expect—that being to mark up a physical location alone. Instead, it’s used to indicate the contact point for the document in which it appears. This element would usually appear in a header or footer on the page.” Sitepoint html reference
so can you?
( )dev.My March 24th
Never heard some before.
( )Martyn March 24th
I’ve come across most of these before but theres a few little odd ones including the . I don’t think I would leave it up to my browser to decide on the page breaks!
I do like the address and cite mark up however.
( )daniel lopes March 24th
fieldset,cite and label are important on the semantic perspective and should be used.
( )Adam Pieniazek March 24th
Nice list. Your #8 live demo seems to not be working (I’m using Safari on Mac Tiger).
( )lawrence77 March 24th
But I used acronym here! Lawrence77 Most of the wordpress comments supports this!
( )its not a rare then!
But all the others are very cool!
thanks for sharing!
Doctor Rock March 24th
They’re “elements” not “tags”. And in the example not applying a element to text adjacent to a radio button input allows both radio buttons to be selected. By using with the matching name to the you can assure only one radio button can be selected, and the label itself is clickable.
( )Jordan March 24th
I have been looking for something like optgroup, i was just using another option with out a value to separate option lists.
thanks
( )Dasani March 24th
You can do all this with css.
( )lowell March 24th
way to miss the whole freakin point of the article. good job.
( )Damjan March 24th
And what about semantic?
( )lowell March 24th
“Rare” HTML tags?
Doesn’t ‘rare’ imply collectibility? It’s kind of difficult to collect intangibles like, well, HTML tags. I think the word you’re looking for is ‘obscure’.
I’ll leave you alone about how you actually used said tags; everyone above me has tore into you enough as it is.
All in all, a disappointing article from NetTuts; it’s like the site is losing its touch. It’d be understandable if this were written by some guest columnist type, but Glenn is a regular contributor here. That’s too bad, I guess one can’t stay at the top forever. Or even readable.
( )Meshach March 24th
NETTUTS is doing fine. If you want more “touch” join there tutsplus+
( )lowell March 24th
no they’re not. and no, i won’t. i disabled adblock on this page. that is good enough.
Doug March 24th
Lowell,
Rare does not imply collectors item. Rare implies “not often found”. Collectors items are usually rare, but so are beautiful women, smart presidents, and guys named lowell who aren’t douche bags.
( )Shane March 24th
Glenn’s always done the ’shopping list’ type of posts. 10 of these, 10 of those.
I prefer the development tutorials, but it takes all sorts of content.
( )Kevin Quillen March 24th
Don’t forget the button tag. Incredibly more useful than input submit
( )Robert Fauver March 24th
Pretty dope, I always forget these. Thanks for sharing.
( )Tim Wright March 24th
Just a few comments:
– I sat in on an accessibility lecture not too long ago and they really ripped using “optgroup”, turns out it’s very confusing to a screenreader.
- acronym is being dropped because of the cloudy definition and overlap with abbr. So we’re using abbr now (personally, I like using acronym over abbr, when there’s gray area).
- while “rel” is a great attribute. Using it to define a clickable region is a bit of a stretch. The AIRA spec now takes care of defining roles for accessibility: http://www.w3.org/WAI/intro/aria (should be finalized soon)
- for “wbr”, there’s a cool css3 property coming out for creating word-breaks, very cool. I’m looking forward to using it.
I think that’s all, good list though, I’ve never used “ins” or “del” before, very cool for editing!
( )Franz March 24th
is a possibiliy to tell the browser to make a line break here if necessary. I use it often in German language with words combined by “-”, because not all browsers brake these combined words: “Print-tastic” -> “Print-tastic”
To “syllabicate” large German words, I use “”, which is unfortunately not interpreted by every browser.
( )Franz March 24th
… I use “& shy ;” (without spaces) …
( )Franz March 24th
Damn … “Print-tastic” -> “Print-<wbr /> tastic”
( )kieoko March 24th
wow, welcome to web 101
any real frontend dev knows these.
( )Igor Escobar March 24th
Weird, all those tags i use often… Except the tenth.
( )Meshach March 24th
Good article.. I knew about all of them but the tag.
( )Jack March 24th
thank you. i read every word!
( )Renzo March 24th
Nice article, I never used any of them yet… I’ll try now!
( )aQuib March 24th
Excellent article! For my 7+ years in web design, there were tags within this article unfamiliar to me.
( )Simon Sigurdhsson March 24th
The wbr tag really contradicts the semantic approach to HTML, so I would personally avoid using it, in favor of appropriate UTF characters. The rest are useful though, and I seriously doubt anyone has failed to notice the label element.
( )Joe March 24th
totally useless
( )Jacob Gube March 24th
If you’re going to use the <wbr> tag, at least self-close it. <wbr />
Also, why do you have a <span> outside of another element like a <p>?
( )Chris Wallace March 24th
Hahaha… Jacob, you rock.
( )Jacob Gube March 24th
Ditto.
Jacob Gube March 24th
Additionally, with regards to “rel”, if the argument is for working with JavaScript, use a class or an id instead because rel is not supported by all browsers. for example, <a class=”clickable”> would be better than <a rel=”clickable”>
( )Diego SA March 24th
Wow, this post has a lot of good tips!
( )I will try it too!
Timothy March 25th
I’ve never had a problem with it. Works in IE6, 7 and 8, as well as FF, Chrome, Safari. What browsers don’t support it?
( )Gopal Raju March 24th
Nice List!
Gopal Raju
( )productivedreams.com
twitter.com/gopalraju
Eduardo March 24th
I use “fieldset” and “label” very often.
( )Helen March 24th
Great article, Glen! Interesting how many people talk about the semantic web but noone is currently using existing tags that makes the code more semantic.
I use on the contact page, and whenever I make an explanation or a definition of an expression someone maybe is looking for, I use the -tag.
The and is a very good SEO-tool, because you have USA and United States of America at the same time in the text whithout bothering people with repetition, and the search engine knows that you are really talking about the United States and not about another kind of USA like the Unbelieveable Sucker Association.
Taking a look at the next generation tags of xhtml I really wondered that these guys didn’t take the chance to create a bunch of semantic tags that enables a machine to discover what a text really contains. Examples:
(image with content) vs. (functional image) vs
(outstanding content that appears on every page and should not be considered to be part of the content)
(visible label line under an image)
(in a new semantic way)
…
( )Helen March 24th
Okay, I made a mistake. Every label I used disappeared in the visible text
Including those ones I invented.
( )Matt March 24th
Wow… that was great!!! Thanks for bringing these to light/
( )Mike March 24th
Good post! I had forgotten some of these (and learned some new ones).
( )doylecentral March 24th
Great underused tags.
( )doylecentral March 24th
<dl> <dd> <dt>
underused tags
( )Marah Marie March 24th
<dl> <dd> <dt>
Incredibly misused tags. They’re for definition lists but somehow designers always seem work them into sidebar columns and people like me always seem to work them into regular inline HTML (body copy) for tutorials and the like. I wish there was an equivalent that was also semantic and offered as much flexibility.
( )Jacob Gube March 24th
I think people are frustrated because this site is frequented by beginners: i.e. people that will be our colleagues and employees in the future. So let me state the things that I feel should either be corrected or removed:
1. Labels and fieldsets are not rare at all. It’s part of web form best practices. It is part of giving your web forms a good structure. Unless you learned web design/development purely from W3CSchools, labels and fieldsets are not rare or obscure at all. Most web developers who actually do web development know this already and to say “one of the most forgotten” implies that it’s rarely used and therefore isn’t important, which it is if you care about a semantic structure and better accessibility. A more obscure ‘tag’ in my experience from working with developers of all levels are <pre> and <code> – it’s a favorite interview question of mine to gauge their knowledge of HTML.
2. the rel example is just not good. I say this because that is poor use of the rel tag. Based on the argument used, it should be a class and ID. Using
relalso invalidates your code so if you care about standards set by W3C, avoid this attribute at all cost.3. rel example again: “and it knows to apply some Ajax“… um… wtf. What does that even mean?
4. The example used in the rel attribute example is NOT “one of many techniques you can use”, you shouldn’t use rel for the example you used – the right way would be through a class or ID for that example.
5. <wb /> should be used in the example, not <wb> if you absolutely must use it. Note that in the reference you used, in the footer section of Quirksmode it says “this page is not valid and is for testing purposes only”
6. In number 10, Should really change <span> to <p> because (a) you should never have a span tag that isn’t enclosed in another element, (b) it would be semantic to do so.
7. If you insist on calling it tags, then there are only 9 ‘html tags’ on here because rel is an attribute of an ‘html tag’.
I hope you truly consider revising some of the errors on this article because new and young developers will be reading this – it’s a big responsibility to make sure that you always share best practices and promote web standards, for the sake of those of us who have to work with the new guys.
( )AliasP March 24th
That’s it, after going through all these comments and nearing brain implosion, I’m switching all my scripts to WHITESPACE.
( )Dice March 24th
IMO, tags should have been mentioned.
( )callum March 24th
great post! very useful, thanks!
( )Janckos March 24th
Muy interesante, gracias.
( )Diego SA March 24th
Wow, there are some tags I didn’t know. I gonna try it later.
( )Andy Gongea March 24th
First, I will tell you this pretty straight: You’re the worst writer from Nettuts from my point of view. Considering the comments, others may share my thought.
All other tutorials offer valuable information while yours show 10 “things” all the time. No offense but if you not technical enough and can’t create a important and valuable information – that’s OK. All you have to do is research and find out. But try and verify your content before sending it to the community.
PS: Thank you guys for this valuable comments. This is a real community.
Cheers!
( )Diego SA March 25th
Hey Dr. Evil!
I’ve never seen such a punch in the middle of someone’s face in a post comment.
I have fear of you! Be cool!
( )Andy Gongea April 7th
That was funny.
But take a look at those newbies that are saying what great tips they found in this article. That is what you should be afraid of. Many new designers wannabes will take this info for granted – this thought gives me the creeps.
mbarvian March 24th
Wow, I haven’t seen many of these. Thanks for posting!
I might start using acronym now!
( )Chris Coyier March 24th
I don’t see how a person can call themselves a “web developer” when they have very little understanding of the most basic thing about web development: HTML. Why didn’t you use a labels for yes and no in the fieldset example? Have you worked with forms before, because if you have, how can you say label and fieldset are rare? If the answer is yes to my question and you have worked with forms before, that’s just sad.
( )Ramil March 24th
label, fieldset and rel are commonly used most of the time.
( )fesh March 24th
Great articles and very useful! I been doing html for more than 5 years and honestly I don’t know what is the use of those html tags! Thanks!
( )Geeves March 24th
is not a valid html 4.01 or xhtml 1 tag. The wbr-element is not part of w3c’s HTML spec at all. That’s the reason the tag is little known or used. My advice would be to stick to standards.
( )Kyle Simpson March 24th
I just want to say I use the wbr tag in my site, and I am happy with it. I have a script that inserts it every 20th character in long unbroken strings of characters, to allow them to break. These are usually long URL’s that are being printed on the page, and so nice wrapping is very helpful.
Also, my script instead uses if on Safari (since safari doesn’t support wbr), and does almost the same thing, but with a printable hyphen at the break point. The combination of the two covers all major browsers and provides nice wrapping.
Standards be darned, there are uses for things like this. And it seems to be well supported at the moment.
( )Kyle Simpson March 24th
btw, I should have known that the character wouldn’t print well. The character I was referring to is ­.
( )Alfero Chingono March 24th
I’ve only used three of these in all my web development years, many thanks.
( )John Davies March 24th
Great article, many of these tags were long forgotten!
RT
( )http://www.privacy-tools.us.tc
David Killen March 24th
Some of these tags are incredibly useful for making use of semantic markup. It always makes sense to use the tag which best describes the content. Tags like and do just that.
( )Swapnil Sarwe March 24th
Whoaaa!!!!
Never heard some of them, and even if heard never really thought about the specific use for which it must have been meant…
Anyways, will love to use them, but only those who validates my HTML clean.
( )Ben March 24th
This article is disgraceful to both newbies who are using it to learn from and REAL professionals who know better.
You know what else is a rare tag? . Double points if you nest it in a . Triple points if you use comic sans and apply it using the tag
The sad part is my sarcastic example is every bit as valid as your example of the REL attribute. If you are going to use it for “AJAX” you’re better off just make up a attribute such as anotherNonValidJunkAttribute=”clickable” because they can be targeted the same in JavaScript but in my example Google won’t read the REL and think that the link is related to “clickable”
( )Mike Piasecki March 25th
Niiiiiiiice! Let me buy you a beer!
( )Frustrated March 24th
Would Mr. Stansberry please stop posting about things most people either already know about or don’t care about.
( )Abhijit March 24th
In these Web 2 days, label and fieldset are pretty commonly used for designing forms; and rel is of course used everywhere. So at least these three are not “rare”. optgroup is also pretty common, though it is starting to become less common now a days mostly because select boxes are being replaced by custom lists.
( )Amanda Kruel March 25th
“If you were wanting to achieve the same effect but without using the tag, you could also try or .”
I love ” ” and ” “!
No, just kidding. You might want to fix that, though.
Anyway, great stuff! Very interesting to see some “new” and more importantly, simple HTML.
( )Rahul Chowdhury March 25th
Man, these tags are awesome. Its really helpful for Webmasters, I will use them in my Websites. Specially the Acronym Tag, its really good and worth using.
( )Abdullah March 25th
WOW, I already know 2 of them only
( )thanks
Mani March 25th
I think, the comments section is more informative than the actual article. And it actually is.
Thanks Paul and Jacob for sharing your thought else many of the readers might not have able to the tags correctly.
But what about those, who do not care to read comments!!
( )Mani March 25th
Sorry, please correct this line:
Thanks Paul and Jacob for sharing your thought else many of the readers might not have able to the tags correctly.
Thanks Paul and Jacob for sharing your thought else many of the readers might not have been able to know the tags correctly.
( )Vsync March 25th
Great great article.
As an advanced web developer I rarely come across an article that
teaches me something new about XHTML :p
but here it is! i didn’t know about this !
great thing this tag!
although CSS3 word-break should replace is very soon..
( )stelt March 25th
Try http://dev.opera.com/articles/view/21-lesser-known-semantic-elements/ instead
( )tom-erik March 25th
wbr is great for long words when listing narrow li’s . You can count letters and add it when the letter count exceeds the li’s width.
( )covax March 25th
Would Mr. Stansberry please stop posting about things most people either already know about or don’t care about.,.
( )Peter March 25th
Great article, I’ll keep it as a reference. Perhaps I’ll use some of the tags in future.
( )web design newport March 25th
If you’re going to abuse semantics instead of using acronym for definitions why not use abbr it’s shorter and there’s at least some rationale behind something like
[abbr title="twitter: a microblogging website"]twitter[/]
Whilst there’s no way “twitter” is an acronym. I just use a span with a class=”defn” attribute and a title then style it to match the acronym and abbr tags. Works the same way then and is more correct.
( )photo sharing March 25th
Wow I’d never heard of
I’ll be giving it a go soon
( )Mike Piasecki March 25th
And coming up, 10 things I’ve eaten in the last ten days, for the tenth time.
Seems the info porn side of web development is getting a little lean in the area of useful information for once.
Now get back to work and do something useful with your time.
( )Mike Piasecki March 25th
I dunno, it just seems like if it’s outside the realm of a CMS, a Bullet Proof Web Design book or AJAX it’s treated as some lost art. Kinda sad really, seeing self proclaimed developers thinking simple HTML or XHTML tags are forgotten or rarely used.
It’s a decent article with some strange examples to support the points made, but over all it went well with the time I had to kill.
( )ATV March 25th
Really useful post
( )Tim March 25th
No tag? This is one of the rarest and most useful tags I’ve come across.
( )Chris March 25th
As someone that is an HTML buff and doesn’t want to make the jump to any automated systems like wordpress, it’s nice to see these commands.
( )Ryan March 25th
I think that I have been living under a rock all this while, the tutorial is really awesome. I like the way the rel tag has been explained.
( )Adam March 25th
At the section, you mention instead of . BTW, great post! Thanks for it!
( )Haha March 25th
I hazard a guess that would stand for “wrapping break”, meaning that the break would occur if the line of text had to be wrapped inside a container or table cell or something. That would be useful today, I can’t stand seeing the amount of widowed and orphaned text on web pages in general.
Anyway, like 1000+ people have said before me, there’s a good reason why alot of these tags are not in use. They’re replaced with better solutions, or CSS. God help you if you use or
( ), or or for that matter.Pirate Pete March 25th
And god help the moderators if they let these obscure tags get through on
( )their forum comment section!Adam March 25th
At the fieldset section, you mention label instead of legend. BTW, great post! Thanks for it!
( )Simon March 25th
the radioboxes don’t work right because you’ve given them different name attributes.
Fine article, i will use the acronym tag more often now.
( )Raza March 25th
Great Work!!!
( )Daan Weijers March 25th
I like the entry, however, like half of these aren’t that rare.
( )Trent Walton March 25th
Good post, you learn something new every day… not too heartbroken that doesn’t validate.
( )Zohaib March 25th
and , and other new tags are coming in html 5
( )http://www.w3schools.com/tags/html5.asp
Bree March 25th
Fun post – WBR was a surprise to me.
( )Brian Bell March 25th
In response to all the complainers… You can never make all the geeks happy. I think the post is great and I appreciate the effort to put this list together.
( )Chris Wallace April 1st
The post is great if you want to learn how to write HTML poorly.
( )Andy Matthews March 25th
Make sure to check our my friend’s site containing lists of commonly underused HTML tags:
http://showmehtml.com/
( )anom March 25th
wbr is invalid markup!
( )anom March 25th
document.write(’xss’);
( )Your Sash Staff March 25th
Great list of tags. The cite one is very useful, thanks for sharing!
( )bucktowndigital March 25th
stellar list
( )Lisandro Grassini March 25th
The TABLE tag should be in this list instead of LABEL… I use the LABEL tag all the time in order to create forms without tables. Regards!
( )CHose March 25th
Most are useless… just use styled divs damnit!
( )CHose March 25th
Note that there are characters such as zero-width space or soft-hyphens, that do the same job as the tags described here.
( )Jamp Mark March 25th
they are not really rare and they are used on pages where appropriate. i’ve seen them a lot on bibliographies, thesis, survey forms, etc. i agree with you on . it is hardly ever used.
( )Gary Callaghan March 25th
Some very nice tags there that i haven’t seen before, Most of the tags you mentioned should be used more reguarly as they are very handy.
Thanks for this article.
( )The Love of Code March 25th
Nice list. I would say that the rel attribute isn’t really all that rare. It’s starting to show up a lot for various JavaScript/AJAX and SEO tricks.
Your list is missing a set of tags that are rare in my opinion: DL, DD, and DT. The definition tags are rarely seen, but can be quite useful for term definitions or even FAQ pages.
( )Peter C. March 26th
I can only re-iterate what has already been said in the previous comments. Yet another woefully inaccurate article from Mr Stansberry. Here’s to future Nettuts+ articles being much more on-target and faithful to their titles!
( )Dave March 26th
More bugs: Your radio buttons are not linked so you can select all of them at once and on FF3 the fieldset does not draw a box around the fields. (At least, it doesn’t in your example.)
The wbr tag does not have good support across all browsers. More info on Quirksmode: http://www.quirksmode.org/oddsandends/wbr.html
“rel” seems out of place in a list of html tags but, as you said, it can be very useful and seeing it on anything other than link or anchor tags is quite rare.
Don’t forget when making AJAXy things that not every uses javascript. Make sure your links and buttons still work with javascript turned off. Especially in the case of links, this will help your Google ranking as well as not turning away visitors who don’t have javascript turned on. (Like me)
For instance, there are no labels on this comment form. They are placed inline using javascript after the page loads. I can either guess that they are in Name, email, URL format as most blogs use or I can look at the source code and hope that the names are descriptive. For some reason you have used the attribute “defaultvalue” in these input fields which does not exist rather than the more standard “value”… which would have worked. Using a label would have been a much better idea.
I think it would be a better use of your time to run your pages through the W3C validator than to start learning obscure and badly supported tags that add very little benefit to the average user.
( )Steve March 26th
Great Post, I never new they existed…
( )Vole March 26th
should be used for acronyms
acronyms are abbreviations pronounced as words rather than as inidividual letters
radar
laser
( )Trae March 26th
I enjoy the tag. I like to put it on text then specify a brown color with font-weight bold in CSS. Does the trick every time.
( )Gerard Banasig March 26th
I miss the tag =)
( )Gerard Banasig March 26th
I miss the marquee tag =)
( )keruchan March 26th
haha I never use any of them except for the ‘rel’ tag. I guess I’m too young to saw them in action way back decades ago.
( )Debajit March 26th
I think an important “rare” tag that is missing from this list is the q tag.
( )tedeh March 26th
What’s most sad isn’t the fact that this Jesus-esque character “Glen Stansberry” made money on writing this “fine” piece of … article, but that more feeble minded developers are taking these “tips” at face-value, quite possibly applying them in their work. Here’s what I have to say: read the first 20 comments and learn the real deal.
The wbr-tag you say? Why not also enlighten us on the usage of the marquee-tag and the blink-tag too? Haven’t seen those around lately.
( )Nope March 27th
Jesus…you guys are such nit-picky bastards. Does anyone actually code or do you spend every ounce of your time picking through simple tutorials and arguing with each other over correct semantics…and spelling in each others comments. For christ sakes…i could only read like the first 15 comments before i confirmed that i was wasting my time. And yeah, i prolly spelled something wrong.
( )Maria March 27th
Thank you, I wasn’t aware of all of these, but now that I do, I’ll definitely be using a few of them.
( )Martin March 27th
Paul Armstrong – get over yourself.
It is most unfortunate that you used the phrase “Most unfortunate”.
Don’t make the comments your platform for showing how much you know.
Make your points and move on.
Debating whether on not NCAA is an abbreviation. Get a life.
( )Chris Wallace April 1st
It’s not an abbreviation. If you try to teach someone how to spell the word “bark” and they spell it “barc” they would need to be corrected. Sure it “sounds” the same, but it’s not the right way to spell it. When what you’re doing is educating others, you need to be precise with what you say and teach.
( )John March 27th
It’s shopped
( )Dan Gayle March 27th
FAIL
( )Raymond March 27th
Just another comment to read. Everything has been beaten to death in one direction or the other and I wanted to do something telling myself reading all of this was not a total waste of time. Cheers!
( )JohnF March 28th
is no longer supported in IE8
source: http://en.wikipedia.org/wiki/Internet_Explorer_8
( )JohnF March 28th
wbr tag is no longer supported in IE8
source: http://en.wikipedia.org/wiki/Internet_Explorer_8
( )Titifrim March 28th
Good “aide-mémoire” ! is depracated by the w3c on the other hand…
( )Madnerd March 28th
2 other good tags to know too are the and for like 3rd
( )Madnerd March 28th
post took out the tags the 2 are sub and sup tags
( )Scarf*oo March 29th
i can’t quite believe I didn’t know some of those tags. What particularly surprised me is the existence of the optgroup tag. It also seems to work cross-browser.
( )Titifrim March 29th
is missing in my comment, sorry.
( )Titifrim March 29th
<wbr> … grrr
( )Eddie March 29th
Improper HTML in example 7, you haven’t closed the input elements.
( )Tim March 30th
What has happened to the TUTS? There’s an awful lot of sales-pitch lists and poor/under researched content… Why would I consider paying for the TUTS+ stuff if this is the quality diplayed?
( )Daniel March 30th
Those really are rare tags, so rare that I’m not sure if they’re even really very useful.
( )Ts March 31st
thirdsoul.net Visit It !
( )Severeon March 31st
You should have used label’s with your fieldset.
blah
Input one
Input two
Now if you were to click on either the radio button or the label its self you would select the radio button. It is very handy ^^
( )Severeon March 31st
You should have used label’s with your fieldset.
<fieldset>
<legend>Blah</legend>
<label for=”a_id”>Input one</label>
<input type=”radio” id=”a_id” name=”v_radio” value=”1″ />
<label for=”b_id”>Input two</label>
<input type=”radio” id=”b_id” name=”v_radio” value=”2″ />
</fieldset>
Now if you were to click on either the radio button or the label its self you would select the radio button. It is very handy ^^
( )Mo`a March 31st
I hate this website. Too many great tuts and not enough time!!
( )by the time I read one 3 more appear.
Jonatan March 31st
Cool haven’t herd most of them… thanks for sharing!!!!!!
( )E11World March 31st
label and fieldset are not rare though.. still, good list.
( )sOKObANJAC April 1st
great tuts
( )devolved April 2nd
Sorry to tbe the fly in the ointment but you really are missing some important stuff here and its quite typical of the semantically challenged.
1) acronym is not for adding info about something, if you want to do that use a span. It’s a *specific* form of abbreviation NOT expansion. YMCA, FBI etc are acronyms.
http://en.wikipedia.org/wiki/Acronym_and_initialism
2) abbr – even though this is a great tag (even though ppl use acronym instead wrongly) it’s not supported by ie6/7 [and probably 8] so nothing will show up if you use it.
Was hoping for an informed article but this fails, epically.
( )dpro April 2nd
Nice tips, but I even like the comments more!
( )Paul April 3rd
The and tags seem very useful! Search engines can pick these up well? Interesting post!
( )Hashim April 4th
Thanks for the rare tags info! I found really useful in my recent project.
( )Mike April 4th
Nice list. However, your fieldset example doesn’t work. You need to have the name attribute be the same. Since your example uses different names, they will both be selected instead of one OR the other.
( )Vertjaars April 5th
Optgroup was AMAZING!
( )Why haven’t we seen this in popular usage yet?
Aamer Abbas April 5th
Facebook uses the tag quite well to wrap names and certain other elements that they need to show in limited-width boxes.
In my opinion, this is great, yet highly underused tag.
( )Aamer Abbas April 5th
Oops, looks like my markup was cut out of the comment (perhaps interpreted as literal HTML).
What I meant to say is that Facebook uses the “wbr” tag quite well.
( )Kp April 10th
This stretched my brain a bit. Mad props. Great design, love it.
( )tagnu April 20th
Last point. wbr tag.. “you could also try or . “” ?? What’re the other tags?
( )Thanks for the article
aaaa April 27th
bad
( )aaaa April 27th
very bad,,,dnt u know anything about html???rel is not a tag…its attribute…u stupid…stop posting these tags on net
( )David April 28th
Your definition of the tag is wrong : you say it «defines a group of words» but, as its name says, it actually defines an acronym… «Twitter» isn’t an acronym, «SEO» is.
( )Signupandmakemoney May 1st
Yeah, I really don’t use those HTML tags at all. I’m trying to figure out how to get a list arrow for my css navigation pane. Anyone’s input would be greatly appreciated.
( )Rajbir Jawanda May 8th
Tag 2. is something nice.
I implemented something equivalent using some funny logic of having space in front of normal list items.
Impressive compilation.
( )Dir Submitter May 28th
I was prepared to reply after the first half of tags and brag that I got to use them all. But I have to admit, the last one: wbr is the one I didn’t use.
btw I think wbr is no longer supported in ie8. Microsoft just wants to be special.
( )ddsign June 15th
I find this post very interesting ,so I am going to make a translation to Spanish in my blog. Thanks for writing it!
( )oasis1984 June 19th
Great Articles…. Thank.
( )Phaoloo June 21st
Actually, I never use one of them before. Common tags are enough for me, but it is great to know more
( )vasudev July 23rd
Good article. But please confirm is that correct acronym tag example ?
( )Justin Staple October 21st
Just spotted a syntax error in the description of the tag.
“…but the benefits are many for screen readers…”
I think ‘many’ should be ‘mainly’
( )Lahore October 24th
Thanks for sharing this info. This was very helpful and educational
( )