Observed Signal · Apr 20, 2026 · Technical Release · Source: https://developer.chrome.com/static/blog/feed.xml · Impact: 4/5 · Sentiment: Positive
Chrome starts final Soft Navigations origin trial
Google's Chrome team announced an origin trial for the Soft Navigations API running from Chrome 147 to Chrome 149, preparing to ship the API later in 2026. The API standardizes detection of JavaScript-driven 'soft navigations' used by Single Page Applications so browsers and third-party scripts can measure Core Web Vitals for those navigations. It introduces new performance entries (SoftNavigationEntry and InteractionContentfulPaint), a navigationId to attribute entries to navigations, and a largestInteractionContentfulPaint attribute. Developers are asked to test via flags, command-line options, or the origin trial and to provide feedback and bug reports on GitHub and Chrome's issue tracker. Chrome DevTools already surfaces soft navigations in traces as of Chrome 145.
A technical release from a major platform (Chrome/Google) that standardizes how soft navigations are detected and measured, enabling consistent Core Web Vitals measurement for SPAs—impacting RUM, site performance metrics, and tools used by publishers and analytics vendors.
Track Chromium Signals & Market Shifts in Real-Time
Polaris7 autonomous intelligence agents track regulatory filings, primary sources, executive changes, and deal flow 24/7. Create your free Explorer workspace to monitor these entities.
Key Takeaways & Evidence Grounding
- Chrome announced an origin trial for the Soft Navigations API running from Chrome 147 until Chrome 149.
- The Soft Navigations API adds two new performance entry types: SoftNavigationEntry and InteractionContentfulPaint.
- The API expands existing performance entries to include a navigationId for attributing metrics to specific navigations.
- Chrome DevTools shows soft navigations in Performance traces starting in Chrome 145.
- The API now treats history.replaceState as a soft navigation in this iteration.
Connected Companies & Entities
3 Entities mappedOntology Mapping & Concepts
Related Market Signals & Shifts
Recent verified developments and strategic activity across this market segment.
Chrome starts origin trial for Container Timing API
Chrome announced an origin trial (starting in Chrome 148) for the Container Timing performance API, a new web platform feature that measures render timings for groups of elements (containers) rather than individual elements or the single largest paint. Developed by Bloomberg and implemented in Chrome by Igalia, Container Timing uses a containertiming attribute and PerformanceObserver entries (type "container") to report first-render, latest-paint, painted area, and last-painted-element for named containers. The feature is available behind flags in Chrome 147 and via origin trial tokens from Chrome 148 so sites can test it on real users. The post includes examples, best practices, feature-detection guidance, links to the spec and GitHub issues, and asks for feedback via the WICG repository.
Chrome 149 Beta Released
Google published the Chrome 149 beta on May 6, 2026, describing new browser platform features across CSS, Web APIs, and origin trials for Android, ChromeOS, Linux, macOS, and Windows. Notable changes include new and extended CSS capabilities (support for path(), shape(), rect(), xywh(), image-rendering: crisp-edges, and a new path-length CSS property), scoping system accent color exposure to installed web apps to reduce fingerprinting, and behavioral tweaks like clipping text overflow during user interaction. Web API updates include programmatic scroll promises, Request.isReloadNavigation, WebSocket handling for bfcache, and Payment Request improvements for distinguishing internal errors. Chrome 149 also opens origin trials for features such as a focus-without-user-activation permissions policy, an event-driven Gamepad API, and WebAssembly custom descriptors.
Chrome launches HTML-in-Canvas API origin trial
Google's Chrome team announced an origin trial for the experimental HTML-in-Canvas API, which lets developers render live, interactive DOM content directly into 2D canvas contexts or WebGL/WebGPU textures while preserving accessibility, text selection, and browser integrations. The API exposes methods such as drawElementImage, texElementImage2D and copyElementImageToTexture, plus utilities to synchronize CSS transforms (getElementTransform). The feature is available for testing via an origin trial (Chrome 148–150) and in Chrome Canary (Canary 149+) behind the chrome://flags/#canvas-draw-element flag. Frameworks including Three.js and PlayCanvas already offer experimental support and several demos and examples are published by the community.
Track Real-Time Market Signals & Shifts
Set up custom watchlists to receive automated, evidence-grounded executive digests whenever material signals or shifts occur across your tracked landscape.