HTML 5 wins over XHTML 2.
This post actually echoes my first post on the subject (in French). Here we are, another hedge to cross for Mauritian web designers and companies. Too bad, just at the moment when Mauritian companies like E-services have started going towards web standards (repect for that though there’s still a lot to do). So, what is this hedge, the dropping out of XHTML. Yes Sir! XHTML is dead. Well metaphorically.
When?
The W3C has announced last week that it will be dropping XHTML 2 and allow more resources to the HTML 5 workgroup. This means that the expected date of use of HTML 5 is getting nearer. FYI, it was expected in 2022, now just give it 3-5 more years. So, the first question is: why are they dropping XHTML and what to expect from HTML 5?
Why?
There’s one simple thing to take into consideration. How come we all used IE6 at one time (about 90% of the world population having access to the web at that time did) and went completely mad when more reliable and standards bases browsers came out? The answer is: most browsers at that time followed HTML. Standards were vague and HTML, being very permissive did that pages were rendered quite nicely even if there are errors in the code.
XHTML has never catered for errors (at least for critical ones). You mess up a tag, you mess up a site: simple. This is the reason why browsers such as IE 6 had trouble reading such code because they hadn’t been coded to fully understand that code. Going back to HTML will allow web designers to cater for these past generation browsers more easily. No more MSIE_CSS.css and no more hacks then.
What a change! This, however is not over. The change will also occur in the code. How? Semantics. With the rise of web standards we have started to build websites on a semantic basis. We usually use the “document” ID, the “nav” ID, the “header” ID when styling our pages. These selectors have been so much used that they will be given due respect in HTML 5. We will now have new block elements such as
How?
How to cope with this, how to change, what code to use? These questions must be running through some web designers’ minds. Calm down. If you had the good idea of jumping into the standards wagon, you’re in for some change but nothing drastic. The HTML 5 will not be here that soon but you can cater for it by switching back to HTML 4. You can however continue to code in XHTML if you’ve become a code guru. The future browsers will still implement it but you’ll still have to code-hack older browsers.
I hear some who are complaining about the loss of strictness in code. You can actually carry on building on strict code in HTML 4 Strict. It still holds in place and allows you to implement rock-hard robust code.
Conclusion
Few people had expected this sudden change in our everyday job. I mean, some of us have, at some point or another, spent weeks switching to standards and are now a bit astounded to have to go back to that code we tried to go past. This however goes for what the web and web standards stand for. Access to information to everybody in equality disregarding his/her components be they old school browsers. HTML 5 will be giving this back to the web either we like it or not. Anyway, it is a great challenge lying in front of us and it will also be fun to see the changes and work on them. I’m actually really thrilled about this.
More From webdesign
- I increased my traffic by 179%, find out how.
- Driving targeted traffic to your site: 3-5% bounce rate!
- 5 tips to a successful seo-oriented web project.
webdesign Recommends
- Ping.fm – Manage all of your social networks with one! | Ledfrog.com (Brandon Hann)
- Apple iOS 5 Features (Brandon Hann)
Category: Standards and code



![Recommend [webdesign]](http://s3.amazonaws.com/arkayne-media/img/badge/logo-recommend-badge-medium.png)



The end user should have priority over the semantics wars … if HTML 5 will be better for us users, then let it be
Well, on my side it is quite clear, the semantics is for the end user and HTML 5 somewhat helps in this.
Non! XHTML li mem mari. Pa capav fini abitier avec XHTML et astere W3C au lieu impose standar, p ecoute banne lobi.
HTML5 ine fini coup video. XHTML li mari clean et li zoli. To fou ene erreur, to ene c****d dans XHTML. Bsin fou W3C ene bater tro reste avec dimoune et lobi.
XHTML li mo choix premier en langage web. Sependan si ena nouvo standar ene compagni bizin propose client se ki fer sa standar la. Si W3C inn pran decision coum sa be bizin accepter li. Dan le ka kontrer nou pou perdi clian ek prozet.