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?
W3C and WHATWG to work together to advance the open Web platform | W3C Blog
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.
Responses
Related links
Hitler reacts to the HTML5 URL normative reference controversy
This is hilarious …for about two dozen people.
For everyone else, it’s as opaque as the rest of the standardisation process.
Shallow Thoughts » srcset vs. picture
A well thought-out evaluation on responsive images from Bridget.
[whatwg] The blockquote element spec vs common quoting practices
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.
You can use Web Components without the shadow DOM
So what are the advantages of the Custom Elements API if you’re not going to use the Shadow DOM alongside it?
- Obvious Markup
- Instantiation is More Consistent
- They’re Progressive Enhancement Friendly
Hyper-responsive web components | Trys Mudford
Trys describes exactly the situation where you really do need to use the Shadow DOM in a web component—as opposed to just sticking to HTML web components—, and that’s when the component is going to be distributed and you have no idea where:
This component needed to be incredibly portable, looking great on any third-party website, in any position, at any viewport, with any amount of content. It had to be a “hyper-responsive” component.
Related posts
Testing HTML5
A dConstruct workshop reveals some issues with the HTML5 spec.
HTML5 and me
My petitions to the makers of markup.
The HTML5 Equilibrium
Inside the troubled mind of HTML5.
Manual ’till it hurts
Try writing your HTML in HTML, your CSS in CSS, and your JavaScript in JavaScript.
Displaying HTML web components
You might want to use `display: contents` …maybe.
# Liked by Chris McLeod on Tuesday, May 28th, 2019 at 3:14pm
# Liked by Jacky Alciné on Wednesday, May 29th, 2019 at 4:12am