On Friday Jeff Croft posted a piece titled Web Standards Killed the HTML Star where he makes the argument that just knowing HTML and CSS is no longer enough to get a job. He states that the web standards movement has effectively rendered the need for specialized knowledge of browser…
If you’ve been following the latest chaos in the responsive image debate, you may know that there is a battle afoot between supporters of src-n, srcset and picture. If you don’t believe me, I refer you to this WHATWG post, a polite round-up of today’s bar fight. Key is that…
When I saw main proposed as an element a few months ago (or content or maincontent as alternate names), I didn’t think the process to fold it into the HTML specification would move very quickly. Much to my surprise on the W3C HTML Working Group mailing list the main element…
Just over a year ago now I covered how the HTML5 specification is going to allow the alt attribute to be excluded from img elements under some very specific circumstances (Image alt Attributes Not Always Required in HTML5 and More on Image alt Requirement in HTML5). The one I am…
TL;DR: This is just a recap of what’s happening now. If you are up to speed as of today, you can just skip to my brief opinion. Background As I mentioned in my post iPad Retina Display Concerns and Tips, even Apple, with over a year of the Retina Display…
As of Monday, April 23, The W3C has announced that it is looking for a new editor for the HTML Working Group specifically tasked with shepherding HTML5 through the process until it reaches a formal recommendation. Ian Hickson (Hixie) made the request for a call for his replacement so he…
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…
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…