The trend continues where I speak to clients, vendors, young developers fresh out of college, and even the teachers/professors who instruct them and they don’t understand that HTML5 and CSS3 aren’t the same specification. I have repeatedly shown an HTML 4.01 site with CSS3 to explain that they are each…
Mostly I wanted a title with a little alliteration (like that sentence). What I am talking about in the title are vendor prefixes for CSS, those little bits of words and dashes that appear in front of what would otherwise be a W3C CSS declaration, but denotes that this one…
Now that HTML5 is starting to crack the mainstream, misunderstood and misrepresented though it may be , it makes sense that more and more developers and contributors should start to struggle with the shifting assignment of semantic meaning to the HTML5 elements. I wrote about this on Halloween in my…
Last Monday I wrote about some recent changes to the WHATWG HTML5 draft spec (HTML5 kills [time], Resurrects [u]), which then lead to my post discussing how the process to adjust the HTML5 spec only serves to confuse developers (End of <time> Is Not Helping the Case for HTML5). Then…
The decision to allow <time> back into the HTML5 fold has been made. Just like that, one element is restored. This recent dust-up still tells me that all the elements are always in peril. You can read the full decision in the email archives. This section of the email describing…
Yesterday afternoon I posted a general overview of recent changes in HTML5, focusing on this weekend’s development over the removal of <time>: HTML5 kills <time>, Resurrects <u> I thought I was already a little late to the party, but apparently not so. With the start of the week people swung…
The HTML5 specification as managed by both W3C and WHATWG is an unfinished, incomplete specification that can change at any time. That isn’t a criticism, it’s just a statement of fact. It’s a fact often ignored by people and companies who choose to implement it and then cry foul when…
Guns don’t kill people, the bullets do that (unless you pistol-whip someone to death, which means you probably ran out of bullets). Similarly HTML5, JavaScript, CSS and even Flash aren’t dangerous on their own, but in the wrong hands and with the wrong motives they can do harm. I wrote…
You may recall from my post in February, WebM, H.264 Debate Still Going, that the H.264 video codec is considered patent-encumbered (which resulted in its dismissal from the HTML5 specification) and Google has argued that its own WebM / VP8 codec is made up of patents it owns, releasing it…
This photo represents some of the technologies (pint glasses) that HTML5 (t-shirt) is thought to encompass (drink). The horror of that concept is represented by the hands (defensive wounds coming).I had the pleasure of sharing some pints with Bruce Lawson and Chris Mills last week in London. While discussing what…
This article was originally posted on evolt.org, an online resource for web developers, maintained by web developers. I have granted evolt.org the right to use this article on its web site, and it is the only entity with the right to reproduce it. While spending some time hacking through experiments…
It’s only been 13 years, but CSS version 2.1 is now officially a W3C Recommendation — essentially meaning the specification is final. Which of course means you are now all free to use it in your web pages. CSS2 became a W3C Recommendation on May 12, 1998, over 13 years…