Browser engines, platform APIs, interoperability and web standards.
Showing 1–2 of 2 dossiers
Chrome 153 introduces a breaking provider-integration change in the Email Verification origin trial: issuance requests move to JSON with HTTP Message Signatures. Chrome has also extended the experiment through 156, making the migration more than a one-release test detail while the underlying protocol remains experimental.
Chrome starts a two-week stable cadence with Chrome 153 in September 2026, while Firefox begins its transition with Firefox 155 Beta. Web teams should expect faster browser-version turnover and adjust CI, beta testing and enterprise support assumptions accordingly.
The web platform advances through standards work and browser implementation, often long before a feature becomes a familiar line in a framework. Interoperability, accessibility, privacy and performance all depend on what engines actually ship, not just what a proposal promises.
This page follows consequential browser releases, standards decisions and platform APIs. BTN connects specifications, compatibility data and implementation notes with the practical question of when a feature is safe to use. Coverage also examines policy or engine changes that alter the open web itself. The aim is to give working developers useful timing and context without turning every experimental flag into a production recommendation.
Privacy changes, extension policy and browser distribution also shape what developers and readers can do online. Those stories are covered when they alter a meaningful platform boundary. The standard is practical consequence: clearer capability and compatibility guidance, backed by the specifications and browser material that support it.