When building a website, it's important to add a DOCTYPE declaration at the very top of your HTML or XHTML source code. In most cases, putting anything at all before the DOCTYPE (even whitespace!) will result in some browsers falling back to "quirks mode", causing your site to render improperly. Spelling and capitalization both matter, so often the easiest thing to do is copy and paste the particular DOCTYPE you want. But how do you know which to choose?
The current HTML standard is HTML 4.01, while XHTML authors might choose either XHTML 1.0 or XHTML 1.1. The most commonly quoted reason for using XHTML is that it enforces good coding practices such as proper nesting, consistent capitalization and quoting, etc. Don't listen to that crap; if you develop good HTML habits, you'll do all of that anyway. The differences are outlined at W3.org, but the main differences include capitalization of elements and attributes, and empty tag style:
<!-- Empty tags in HTML -->
<p></p>
<br><br>
<img src="/img.png">
<!-- Empty tags in XHTML -->
<p />
<br /><br />
<img src="/img.png" />
If you are concerned about cross-browser compatibility, I strongly suggest you use a strict DOCTYPE. Relying on transitional DOCTYPEs may require revision as deprecated features become obsolete features in newer browsers. Relying on "quirks mode" usually requires you to do more work such as adding IE hacks to your HTML and CSS via conditional comments.
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<-- HTML 4.01 Strict -->
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<-- HTML 4.01 Transitional -->
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN"
"http://www.w3.org/TR/html4/frameset.dtd">
<-- HTML 4.01 Frameset -->
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<-- XHTML 1.0 Strict -->
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<-- XHTML 1.0 Transitional -->
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Frameset//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-frameset.dtd">
<-- XHTML 1.0 Frameset -->
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<-- XHTML 1.1 -->
Unless you are serving application/xhtml+xml to a known set of visitors (the average internet wanderer's browser cannot necessarily understand application/xhtml+xml), I suggest using either HTML 4.01 Strict or XHTML 1.0 Strict.
HTML5 has its own DOCTYPE, and interestingly enough it may be a good choice for standards-loving developers, even those who are not yet using any HTML5-specific content. It looks like this:
<!DOCTYPE html>
Short and sweet. What's great about this is that all DOCTYPE-sniffing browsers (including Firefox, Safari, Opera, and even IE5/6/7/8) will render in Standards Mode regardless of whether or not they support HTML5. If you're already using a strict HTML or strict XHTML DOCTYPE to induce Standards Mode in your visitors' browsers, you can switch to the above DOCTYPE whether or not you plan to incorporate HTML5 in your website.
I'm a Front-End Engineer at Yahoo! working on the Mail and Messenger teams. I blog about web design and development topics including accessibility, usability, performance, and developing HTML / CSS / JavaScript applications on Appcelerator Titanium and Adobe AIR.
If you're a web developer, you might enjoy Jelo, my JavaScript library.
A few panoramic shots I took at SDCC 2010. #geek http://bit.ly/bwX6GB
JS version of Regex prime number checker:
function isPrime(n) {
return Array(n + 1).join("1")
.search(/^1?$|^(11+?)\1+$/) == -1;
}
Погрузился в пучину EcmaScript5, местами увлекательно, местами нудно =)
Modernizr http://ow.ly/18njQ1
A Collection of 20 HTML5 Video Players - a round-up of JavaScript and html5 alternatives to Flash-based media player... http://ow.ly/18njQ2
jQuery TOOLS - The missing UI library for the Web http://ow.ly/18njQ3
Contactable - A jQuery Plugin | the odin http://ow.ly/18njQ4
Giants vs Dodgers, sweet seats. http://twitpic.com/2ag9pa
@snookca That'll be fixed next week. I promise.
@snookca I was tryna not name names ;) But really that was just par for the course today, pretty hectic day. As I'm sure you know.
Who breaks major stuff after 4pm on Friday? On the last day of the sprint, no less. Tsk. (wasn't me)
Awesome live git tracker for teams: http://www.utsup.com/
RT @DerrenBrown: Blog post: Camera Software Lets You See Into the Past http://bit.ly/9kjVg5
10 invites to the new version of Digg: http://bit.ly/dqM8EV
Threaded vs Evented Servers, great look at the whats and whys. http://bit.ly/bDUEjn #geek
Nav, Context menus, "app-style" toolbars in sample chapter http://bit.ly/csTRY8 of new YUI book http://bit.ly/cJINoV
Add a side-mounted End Call button to your iPhone 4: http://bit.ly/cGxPBD #funny #geekAll original work on this site is covered by a Creative Commons Attribution 3.0 license unless otherwise specified.
You may share or use any code or images from this site in any manner, for free, so long as reasonable effort has been made to give credit where due.
The views expressed in the posts and comments on this blog do not necessarily reflect the views of Yahoo!