Skip to main content
Topic: Hey HTML5 doctype? (Read 6602 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Hey HTML5 doctype?

Just wondering if it's worth jumping in the HTML 5 pond. Lotsa people do it, so it's not necessarily fatal, and it brings some handy perks wth it. We don't really need to stick with older doctypes if we don't want to.

Random example: http://www.w3.org/TR/wai-aria/ This stuffz is great for a11y but wont validate under anything but HTML5.

http://www.paciellogroup.com/blog/2011/06/html5-accessibility-chops-aria-validation/

Which is a bit of a bummer.
Master of Expletives: Now with improved family f@&king friendliness! :D

Sources code: making easy front end changes difficult since 1873. :P

Re: Hey HTML5 doctype?

Reply #1

Ok, you talkative types :P I'm going HTML5 on my guinea pig anyway. Just decided to go for it this morning. Too many benefits, not enough drawbacks, IMO. :)
Master of Expletives: Now with improved family f@&king friendliness! :D

Sources code: making easy front end changes difficult since 1873. :P

Re: Hey HTML5 doctype?

Reply #2

HTML5 for the win. The mobilz theme has it already too. Do it and shut up already! ;)
Success is not the result of spontaneous combustion, you must set yourself on fire!

Re: Hey HTML5 doctype?

Reply #3

I haz valid HTML5 on 1.1.x.  :D
Master of Expletives: Now with improved family f@&king friendliness! :D

Sources code: making easy front end changes difficult since 1873. :P

Re: Hey HTML5 doctype?

Reply #4

Well the change is not to bad, just a bunch of busy work to remove the depreciated tags etc ....

Would we use modernizr as well?

Re: Hey HTML5 doctype?

Reply #5

Dunno. Depends what tags we want to use. Modernizer does generate a whole pile of poo, so if it's not useful poo then I might be inclined to avoid it.
Master of Expletives: Now with improved family f@&king friendliness! :D

Sources code: making easy front end changes difficult since 1873. :P

Re: Hey HTML5 doctype?

Reply #6

You'd be surprised how much busy work is involved in pull out the deprecated tags assuming you also bother to strip the / nonsense (which is still valid, as I understood it)

Nao spent days and days on it, IIRC...

Re: Hey HTML5 doctype?

Reply #7

I can imagine it would be a time blackhole

I changed it just to see what errors / warnings the validator tossed out and it was considerable ... nothing major (on the few pages I checked), but not an few evenings worth of effort either. 


Re: Hey HTML5 doctype?

Reply #9

My 2c: stuff Modernizer. If they can't even spell, I'm not going to trust their code. :P

We probably wont be using all that many of the new tags, because we simply wont need them. So we can just do something like this if we are worried about IE8:

Code: [Select]
	<script><!-- // --><![CDATA[';
if ($context['browser']['is_lte_ie9'])
echo '
document.createElement("article"); document.createElement("aside");
document.createElement("details"); document.createElement("figcaption");
document.createElement("figure"); document.createElement("footer");
document.createElement("header"); document.createElement("hgroup");
document.createElement("nav"); document.createElement("section");';
Rough example with ends tags missing. You get that.
Master of Expletives: Now with improved family f@&king friendliness! :D

Sources code: making easy front end changes difficult since 1873. :P