Browsers situationship: when browsers agree but the spec doesn’t

2026-09-25

Rakhi Sharma looks at what happens when Chrome, Firefox, and Safari ship the same behavior that the spec never described. Sometimes the browsers get fixed, sometimes the spec moves toward reality: newline normalization in HTML forms went that way. WHATWG’s working mode, Web Platform Tests, and the Compatibility Standard all push toward convergence.

atbrakhi.dev/blog/browsers-situationship

Tags browser interop

September 16
WebKit features in Safari 27
83 new features including customizable <select>, scroll anchoring, WebAssembly JSPI, and ariaNotify().
September 15
Firefox 156 release notes for developers
Substitution functions in DevTools, priority-preserving yields, and Promise.try() pass-through.
September 14
The browser’s main thread is expensive
Splitting, batching, and offloading work to keep every frame under 10 milliseconds.
September 10
What’s new in Chrome 153
Capability elements, single-axis scroll containers, and joint iteration.
September 9
You don’t need initial-scale in your HTML
Two authors landed on the same viewport meta element finding hours apart.
September 7
Submit your proposals for Interop 2027
What browsers look for: a stable spec, automated tests, and evidence of real pain.
September 3
Feature detecting “undetectable” CSS features with @supports named-feature()
The CSS Working Group’s answer to detecting behavior changes, not just parsing.
September 2
Firefox 155 release notes for developers
attr() for any property, the progress() and alpha() functions, font-width, and Promise.allKeyed().