HTML

Chrome 135 (in Beta as I write, probably stable early April?) will have customizable select elements in it. You opt-in to it in CSS, and once you have, you can go ham on styling regular ol’ <select>, <option>, ‘n’ friends elements. Very progressive-enhancement friendly as a select without custom styling is… fine. It’s interesting and […]

Seriously almost every “menu” and “tooltip” could and should use this when it’s ready.

For who-knows-what reason color inputs only show a color swatch, not a string representation of the color. Let’s see if we can fix that.

There is some low-hanging web performance fruit with images. Serving them in the right format, from a CDN, with the right HTML can be a big perf win.

The typical approach for these inputs is using multiple HTML inputs, one for each character. But is that a good idea?

Just in case you didn’t know, you don’t need a page to have ID’s on elements anymore in order to jump down to a particular place. We’ve reached support across all major browsers to link to Text Fragments, like: https://frontendmasters.com/courses/#:~:text=Web%20Performance%20Fundamentals%2C%20v2 The #:~: syntax is kinda funky, but here we are, and it’s not too hard […]

When we published our advice on the simplest and best way to take some static local files and make a proper online website out of them, we recommended Netlify. That holds true. But there is some trepidation, as once in a while you’d hear a horror story about usage blowing up unexpectedly and a user […]

Accordion details, toggle switches, styleable selects, responsive video, and more!

𝐏𝐨𝐭𝐚𝐭𝐨 is not just Potato formatted.

Heydon blogged about <blockquote> and Michelle blogged our collective sigh at how unfortunately hard the simple act of quoting something is. You’re not supposed to put a <cite> inside the <blockquote> which I find obnoxious especially because the screenreader situation seems fine with that pattern (this WordPress blog does it that way by default). Adrian […]