HTML

Google Translate doesn’t change the `dir` of a site when translating from LTR to RTL… but you could.

A rare fundamental change to browser default stylesheets: <h1> elements used to get smaller the more <section>s they were nested within, but no more. I would guess because the HTML Outlining Algorithm never really materialized.

Is there a perfectly clear and reasonable answer? Or could we get this someday?

Sometimes pretty simple HTML elements have a lot of things to consider and take care of, from interactivity, styling, accessibility, and more.

The fourth issue of The HTML Review is out. Wonderful writing framed by entirely different and unusual interactive interfaces, brought to you by the power of web technology. A zine come to life. Just try to pick a favorite.

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?