Jeena
The question is why do we need it if there is only one browser engine left (the Google one). Isn’t whatever they implement automatically the standard? Why do we need to waste so much time and energy on some 3rd party coming up with standards?
It’s Armistice Day in the world of HTML:
WHATWG maintains the HTML and DOM Living Standards.
W3C stops independent publishing of a designated list of specifications related to HTML and DOM and instead will work to take WHATWG Review Drafts to W3C Recommendations.
It feels like the loop is finally being closed on what I wrote about in the opening chapter of HTML5 For Web Designers back in 2010.
The question is why do we need it if there is only one browser engine left (the Google one). Isn’t whatever they implement automatically the standard? Why do we need to waste so much time and energy on some 3rd party coming up with standards?
This is hilarious …for about two dozen people.
For everyone else, it’s as opaque as the rest of the standardisation process.
A well thought-out evaluation on responsive images from Bridget.
I’m getting behind Oli’s proposal to allow non-quoted footers within blockquotes in HTML. Here’s where I quote the design principles to support his case.
This episode of the Shop Talk Show is the dictionary definition of “rambling” but I had a lot of fun rambling with Chris and Dave!
Progressive enhancement is about building something robust, that works everywhere, and then making it better where possible.
A dConstruct workshop reveals some issues with the HTML5 spec.
My petitions to the makers of markup.
Inside the troubled mind of HTML5.
Here’s an HTML web component you can use if you’re participating in the origin trial for the Web Install API.
Have you got the perfect talk for this event? Let me know!
2 Likes
# Liked by Chris McLeod on Tuesday, May 28th, 2019 at 3:14pm
# Liked by Jacky Alciné on Wednesday, May 29th, 2019 at 4:12am