This might just be the most nerdily specific book I’ve read and enjoyed. Even if you’re not planning to build a web browser any time soon, it’s kind of fascinating to see how HTML is parsed—and how much of an achievement the HTML spec is, for specifying consistent error-handling, if nothing else.
The last few chapters are still in progress, but you can read the whole thing online or buy an ePub version.
This is such a brilliant idea! Why not allow an img element inside video element in order to provide a responsive, accessible poster image?
It seems like the misguided perception of needing to use complex tools and frameworks to build a website comes from a thinking that web browsers are inherently limited. When, in fact, browsers have evolved to a tremendous degree
This is an interesting proposal for a declarative way of triggering permission dialogs, although it seems to overlap with the work being done on invokers (command and commandfor).
What really disgusts me is to see Google referring to this element as though it’s a done deal. It’s not. It’s a proposal …a proposal that Apple rejects and Mozilla rejects.
Words matter. Call your proposal a proposal, Google.
Update: They fixed it!
Remember when I wrote about sizes="auto"? Well, it’s coming to Chrome! Hallelujah!
I enjoyed this self-documenting journey of exploration.
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.
If the JavaScript API requires a user gesture, maybe it’s time for a new button type.
Some ways of combining security and usability for two-factor authentication on the web.