A handy one-pager for front-end web developers:
Here are ways to keep track of what you can use, of what’s new in web browsers, and ways you can influence the development of the platform by making your voice heard.
So instead of asking “why not React?” we asked: Which of our actual problems would React solve? We went through the list. There were none.
Also, this is good advice when you’re about to make a web component:
Every component starts with the question “does a semantic element already exist for this?”, and remarkably often the answer is yes.
A history of front-end development that culminates here:
The frontier of 2026, the stuff the sharpest people are most excited about, is render the HTML on the server, ship almost no JavaScript, and use the web platform instead of fighting it.
This is excellent advice and I’m glad to see this getting addressed nice and early in the era of customisable select elements:
always provide text content or accessible text attributes for your option elements.
Fixed an issue on iOS and iPadOS where
datalistsuggestions were presented directly over the associated input, obscuring it.
No web standard should require you to agree to an advertising company’s “terms of use.”
I’m genuinely disheartened and angry that the Google Chrome team have done this. Never assume good faith from them again.
This is, hands-down, the most insultingly transparent attempt at web standards bullying I’ve ever seen, including past ones from Google, which is — and I cannot stress this point enough — a company that sells advertisements. This is miles more eyeroll-worthy than AMP, where you’ll recall that a legion of tight-smiling dorks wearing Alphabet lanyards tried to assure us that the only means of survival for the web itself was to funnel all of it through Google’s servers, and only use their very good advertisements instead of those bad other ones.
Going from a carousel on small screens to a masonry layout on larger screens.
A bit of feature detection for a proposed new HTML attibute.
Once again, Safari has fucked up its implementation.
This line-up just gets better and better! You’ll want to be in Brighton on March 12th, 2026.
HTML’s new `command` attribute on the `button` element could be a game-changer.