Skip to content.
Adrian Roselli
Series A Monetization Process RTFM

All Posts Tagged: whatwg

Tables as Responsive Image Containers

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…

Posted:

Tags: browser, css, design, rant, W3C, whatwg

New Main Element Approved, then Blocked

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…

Posted:

Tags: accessibility, browser, html, standards, W3C, whatwg

Image alt Exception Change Re-Re-Requested

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…

Posted:

Tags: accessibility, html, standards, W3C, WCAG, whatwg

Responsive Image Chaos

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…

Posted:

Tags: browser, html, mobile, standards, W3C, whatwg

WHATWG as W3C Community Group in Name Only

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…

Posted:

Tags: html, patents, standards, W3C, whatwg

No DHTML, Please

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…

Posted:

Tags: html, rant, standards, W3C, whatwg

Struggling with Semantics

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…

Posted:

Tags: accessibility, ARIA, html, standards, W3C, whatwg

Even the Return of [time] Is a Painful Process

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…

Posted:

Tags: html, rant, standards, W3C, whatwg

Well, It’s about [time]

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…

Posted:

Tags: accessibility, html, standards, W3C, whatwg

End of [time] Is Not Helping the Case for HTML5

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…

Posted:

Tags: accessibility, html, rant, standards, W3C, whatwg

HTML5 kills <time>, Resurrects <u>

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…

Posted:

Tags: accessibility, html, rant, standards, W3C, whatwg

More on HTML5 as DHTML

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…

Posted:

Tags: Adobe, css, html, JavaScript, rant, standards, W3C, whatwg