W3C has decided to abort the XHTML 2 effort. It is said that this will allow more time and effort towards HTML 5. There were some indications towards lack of interest in the XHTML evolution, so this is not exactly a surprise. [Continue]
skip to navigation | content
ifacethoughtsW3C has decided to abort the XHTML 2 effort. It is said that this will allow more time and effort towards HTML 5. There were some indications towards lack of interest in the XHTML evolution, so this is not exactly a surprise. [Continue]
HTML5 evolution. This is quite in contrast with any other information on HTML5, quite concise and compact. It is quite interesting to see the non-W3C developments that have affected the Web. [Continue]
I had used the Henri Sivonen’s HTML5 validator when I started using HTML5 for this blog. The W3C validator now integrates with that engine. So you can test your HTML5 validation on the W3C validator. [Continue]
This blog is now using the HTML 5 elements to markup the contents. I had this HTML 5 equivalent theme half-ready for a long time, but it was just sitting in my version control as I could put time into finishing it. I decided to activate it today so that it can help me understand more about the new HTML. [Continue]
In the whole backlash of the IE8 announcement, an important piece of information got overshadowed. If you use HTML5, you can skip the effort for version targeting. So, use HTML5 and then you can forget about coding for browsers. [Continue]
There is some turbulence in the web standards group, and a lot of designers and developers I respect and admire are part of it. Molly Holzschlag’s call to fix problems with the future of markup and Javascript got a lot of the community members together. She has also followed up it with the explicit issues, addressing the working group. [Continue]
Elliotte Rusty Harold has explained and illustrated the new elements in (X)HTML 5, which might the future of current (X)HTML versions. These elements impart semantic meaning by explicitly acknowledging existence of a certain structure and elements. Which probably makes (X)HTML 5 more semantic as compared to XHTML 2. [Continue]
Roger Johansson notes that HTML 5 compliant browsers will treat all content served as text/html with the HTML 5 specification. And this means that all of today’s HTML and most of XHTML will be HTML 5. Of course, this is what W3C wants. [Continue]
Mozilla, Opera and Apple have joined hands to propose W3C to accept HTML 5 (via Ajaxian). Not very surprising since WHATWG, the group working on X/HTML 5, was composed of these three. Consequentially Microsoft’s does not appear anywhere near that. [Continue]
Roger Johansson mentioned the new effort by WHATWG towards a community oriented help to sort out the confusion over the present and especially the future of X/HTML 5. help-whatwg.org is a mailing list that you can join to either get or give help to others. Commendable, but I would have preferred a forum, or better a wiki? [Continue]
This is the weblog of Abhijit Nadgouda where he writes down his thoughts on software development and related topics. You are invited to subscribe to the feed to stay updated or check out more subscription options. Or you can choose to browse by one of the topics.