Browser engines, platform APIs, interoperability and web standards.
Showing 1–11 of 11 dossiers
JPEG XL is leaving the experimental-browser niche. Chrome 155 now decodes it by default, but Edge, older installed browsers and Safari's partial feature set still require fallbacks.
SwarmLLM does not route whole prompts to separate machines; it pipelines one model across browser tabs. A MacBook and iPhone can jointly hold Qwen 3.8 27B even when neither device can hold the full 15GB quantized model alone, with no inference server in the loop.
This is not a speculative browser bug. The vulnerable code sits in Chrome’s JavaScript and WebAssembly engine, exploitation is confirmed, and the remediation boundary is concrete: desktop Chrome needs the September 3 patched build or later.
Hugging Face has released 207 Apache-2.0 WebGPU kernels, a JavaScript loader and Fleet, a browser benchmarking service. The package makes kernel contracts and correctness evidence inspectable, but performance remains device- and workload-dependent.
Manifest V2 was already disabled for modern Chrome users. The August 31 change closes the remaining Web Store path, turning any still-pinned legacy install into an effectively frozen artifact with no Store update or reinstall route.
Connection Allowlists turn outbound browser networking into an explicit allowlist for Fetch and other web-platform APIs. The control is opt-in and currently Chromium-only, and strict policies can break legitimate dependencies such as FedCM identity-provider requests if teams omit required endpoints.
WebMCP is no longer a Chrome-only browser experiment: Microsoft Edge now has its own active origin trial, while ChatGPT’s built-in browser and WordPress Playground show agent-client and platform implementation paths.
Chrome extension publishers now face individualized publication caps, with two slots as the default for new or low-history accounts. Existing extensions remain published, increases can be requested, and Google is also retiring the Featured badge while making recent reviews more important to ratings.
WebKit’s Safari MCP server turns browser debugging into an agent-callable interface. It runs locally and makes no network calls itself, but captured page data is sent directly to the connected agent, so browser-session trust and model data handling become part of the development security model.
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.
The faster browser cadence is no longer just a published schedule. Firefox 155 is live and Chrome 153 has begun staged Stable rollout, leaving web teams with materially less time between major compatibility boundaries.
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.