What changed
In September 2026, Chrome's HTML-in-Canvas team documented breaking refinements spanning Chrome 150 and 155. In Chrome 150, WebGL texElementImage2D shed redundant arguments and WebGPU copyElementImageToTexture adopted structured dictionaries. In Chrome 155, WebGL changes to texElementSubImage2D and requires explicit destination texture allocation; WebGPU changes to drawElementImageToTexture. The canvas layoutsubtree attribute becomes content="drawable" and independently drawn nested descendants use drawable. For 2D canvases drawElementImage now returns void while hit-testing/focus geometry synchronizes automatically; 3D canvases must use updateElementGeometry explicitly. The origin trial was extended through Chrome 160.
Why it matters
Developers prototyping accessible game interfaces, charts, creative editors and HTML-in-WebGL/WebGPU overlays face real code breakage between experimental Chrome versions. The revised model aims to keep semantic HTML and accessibility while drawing it into 2D or GPU canvases, but shipping a production dependency on an origin trial carries browser and version risk. Teams should isolate feature detection and preserve conventional DOM or rendering fallbacks.
Breaking API signatures
Chrome 150 simplifies WebGL texElementImage2D and structures WebGPU copyElementImageToTexture arguments. Chrome 155 replaces those paths with texElementSubImage2D and drawElementImageToTexture respectively. WebGL now requires allocating texture backing storage before uploading DOM-rendered content.
Markup and nested drawing change
The previous canvas layoutsubtree flag becomes content="drawable". A drawable attribute on descendants marks independently painted subtrees; nested drawable descendants are excluded from their parent snapshot and may be positioned separately.
Accessibility and pointer geometry
2D drawElementImage no longer returns a transform to be manually copied into element.style.transform; the browser synchronizes DOM hit-testing and accessibility geometry. WebGL/WebGPU cannot infer scene placement and therefore require explicit canvas.updateElementGeometry transforms.
Trial, compatibility and standards status
Google says the origin trial is extended through Chrome 160 and advises renewing trial tokens. The WICG living explainer documents the new primitives and privacy exclusions. It remains an experimental Chromium implementation, not a generally available interoperable API.