699: Jeremy Keith on Web Day Out

What It Covers

Jeremy Keith discusses Web Day Out, a single-day conference in Brighton on March 12, 2025, focused on browser-native web platform features developers can use immediately in production. The conversation covers modern CSS capabilities, HTML APIs, browser support strategies, and the tension between framework-dependent development versus direct browser API usage.

Key Questions Answered

• •Baseline Browser Support: Google's Baseline initiative provides two tiers for feature adoption: newly available (just shipped in all browsers) and widely available (stable for 18+ months). Organizations should use Baseline as a starting point, not final decision, then evaluate whether features are progressive enhancements or mission-critical before implementation. Clearleft publishes their browser support policy at browsersupport.clearleft.com using this framework.
• •Declarative Web APIs: Modern web development benefits when features exist in both declarative (HTML/CSS) and imperative (JavaScript) versions. The declarative version should cover 80% of use cases, like HTML form validation handling required fields and email types, while JavaScript handles complex edge cases. Geolocation and web share APIs need declarative versions rather than separate elements for each feature.
• •Framework Lock-in Problem: React and similar frameworks create bottlenecks where developers cannot use browser features until framework support ships. Document.startViewTransition provides a clean API, but React requires wrapping it in framework-specific components. Browser support matters less to organizations than framework support, creating artificial delays in adopting widely-available features. Developers using raw web standards remain locked out of nothing.
• •Command Palette Pattern: Command-K interfaces proliferate across websites, triggering a palette overlay with keyboard shortcuts. These should use the dialogue element instead of divs because browsers automatically trap focus within dialogue elements when open, preventing users from accidentally interacting with underlying content. This represents asking browsers to handle complex interaction patterns rather than reimplementing them in JavaScript.
• •CSS Adoption Cycles: CSS receives concentrated development attention in waves, with interop initiatives shipping features within one to two years versus previous decade-long timelines. Developers experience fatigue similar to JavaScript fatigue from 2015-2018 when ECMAScript shipped new versions every six months. The cycle now shifts toward HTML features like dialogue elements, invokers, and web components.