Brief
Chrome rolls out HTML‑in‑Canvas API changes in versions 150 and 155
The updates aim to improve ergonomics and align the API with modern graphics conventions.
By Felo News Desk · Published
Chrome 150 and 155 bring a series of changes to the HTML‑in‑Canvas API, according to a Chrome developer blog post published on October 12, 2026.
What happened
In Chrome 150, argument signatures for WebGL and WebGPU were altered to remove redundant parameters such as level, srcFormat, and destType from texElementImage2D. The drawable attribute was introduced, allowing any descendant element of a canvas to be marked for independent drawing. Chrome 155 adds automatic synchronization of DOM hit‑test bounds and screen‑reader focus rings in 2D contexts, eliminating the need for manual style transforms.
What the reports add
The blog explains that developers no longer need to capture return values from drawing methods and pipe them into element.style.transform. Instead, drawElementImage() now returns void, and synchronization depends on the rendering context. For 3D contexts, developers must explicitly call canvas.updateElementGeometry() with a DOMMatrix transform.
What was said
The post notes that the changes respond to community and standards feedback, aiming to improve ergonomics and align with modern graphics conventions. It also mentions that the HTML‑in‑Canvas Origin Trial has been extended, though no direct quotes are provided.
How it came about
The updates follow feedback from the Web Graphics Community Group (WICG) and address earlier limitations where only direct canvas children could be rendered and developers had to manage manual transform synchronization. The blog directs developers to related discussions on the WICG issue tracker for further details.
Key facts
- Chrome 150 removed redundant arguments from texElementImage2D. (developer.chrome.com)
- The drawable attribute now allows any canvas descendant to be drawn independently. (developer.chrome.com)
- Chrome 155 makes drawElementImage() return void and adds automatic DOM sync for 2D contexts. (developer.chrome.com)
- For WebGL/WebGPU, developers must call canvas.updateElementGeometry() with a DOMMatrix. (developer.chrome.com)
- The HTML‑in‑Canvas Origin Trial has been extended. (developer.chrome.com)
Sources
- [1] developer.chrome.com — originally reported as “HTML-in-Canvas updates: Iterating toward a better Web API | Blog | Chrome for Developers”
