Observed Signal · May 1, 2026 · Technical Release · Source: https://developer.chrome.com/static/blog/feed.xml · Impact: 4/5 · Sentiment: Positive
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.
A technical release from a major platform (Chrome/Google) that introduces a new web performance API enabling finer-grained container-level metrics — relevant for analytics, page performance measurement and any ad/UX workflows that rely on accurate render timing.
Track Bloomberg 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 is launching an origin trial for the Container Timing performance API beginning in Chrome 148.
- Container Timing was developed by Bloomberg and implemented in Chrome by Igalia.
- The API uses a containertiming HTML attribute and PerformanceObserver entries of type "container" to emit container-level paint metrics (firstRenderTime, startTime, size, lastPaintedElement).
- The API can be enabled in Chrome 147 via chrome://flags/#enable-experimental-web-platform-features or the --enable-blink-features=ContainerTiming flag; origin trial tokens allow testing in Chrome 148.
- Specification and implementation discussion are available on the WICG GitHub repository; feedback should be raised as GitHub issues.
Connected Companies & Entities
3 Entities mappedOntology Mapping & Concepts
Related Market Signals & Shifts
Recent verified developments and strategic activity across this market segment.
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.
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.
Chrome Origin Trial: Connection Allowlists Network Sandbox
Chrome announced an origin trial (April 16, 2026) for Connection Allowlists, a browser-level security mechanism that creates a network sandbox for documents and workers. Sites can declare allowed network destinations with a Connection-Allowlist HTTP response header; the browser enforces a deny-by-default firewall and blocks connections that do not match the allowlist. The origin trial runs from Chrome 148 to Chrome 151 and initially supports document contexts (workers and some features may be added later). Developers can use a response-origin token to add the response origin dynamically and a report-only header variant to send violation reports via the Reporting API. Chrome invites feedback via the WICG GitHub repository and Chromium bug tracker and provides local testing instructions and an origin-trial registration flow for enabling the feature in production.
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.