This is such a brilliant idea! Why not allow an img element inside video element in order to provide a responsive, accessible poster image?
This is a clever technique for a CSS/HTML only way of just-in-time loading of iframes using details and summary.
dialog, details, datalist, progress, optgroup, and more:
If this article helps just a single developer avoid an unnecessary Javascript dependency, I’ll be happy. Native HTML can handle plenty of features that people typically jump straight to JS for (or otherwise over-complicate).
It’s great to see the evolution of HTML happening in response to real use-cases—the turbo-charging of the select element just gets better and better!
It’s pretty easy to write bad HTML, because for most developers there are no consequences. If you write some bad Javascript, your application will probably crash and you or your users will get a horrible error message. It’s like a flashing light above your head telling the world you’ve done something bad. At the very least you’ll feel like a prize chump. HTML fails silently. Write bad HTML and maybe it means someone who doesn’t browse the web in exactly the same way as you do doesn’t get access to the information they need. But maybe you still get your pay rise and bonus.
So it’s frustrating to see the importance of learning HTML dismissed time and time again.
Turning accessibility awareness into action with HTML.
HTML’s new `command` attribute on the `button` element could be a game-changer.
An alternate route to a declarative version of the Web Share API.
A lazy option for responsive images is at hand.
Don’t replace. Augment.
