Submit your proposals for Interop 2027
What browsers look for: a stable spec, automated tests, and evidence of real pain.
All news — Page 3
Fine, I’ll build my own text editor!
Canvas, contenteditable, and textarea compared for building an editor in the browser.
Feature detecting “undetectable” CSS features with @supports named-feature()
The CSS Working Group’s answer to detecting behavior changes, not just parsing.
Firefox 155 release notes for developers
attr()for any property, theprogress()andalpha()functions,font-width, andPromise.allKeyed().
Modern Web Guidance as a starting point for my own token skills: getting agents to write better CSS
A Baseline-aware skillset from Google, extended with project-specific CSS rules and fallbacks.
Highlighting a range of text inside a form field
The Custom Highlight API finally reaches form controls thanks to OpaqueRange in Chromium 152.
Making a long list fast: content-visibility vs. virtualization
Why unmounting rows costs you find-in-page, anchor links, focus, and per-card state.
What’s new in Chrome 152
Pseudo-element events, device performance tiers, connection allowlists, and relative alpha.
Balancing flex items with flex-wrap: balance
Five ways to avoid an orphaned item on the last flex line, from container queries to one property.
Intent to ship: JPEG XL
Firefox ships the format with the Rust jxl-rs decoder, progressive rendering, and lossless wins.
A look at the
<geolocation>HTML element and how it worksChrome 144 ships a permission-friendly element with autolocate, watch, and a
:grantedpseudo-class.
My HTML boilerplate in 2026
A commented head section with text scaling, SVG favicons, markdown alternates, and fediverse tags.