Shipped September 29: Chrome's post about HTML-in-Canvas changes, the experimental API that lets HTML render inside a canvas. The interesting part for the rest of us is not the API itself; it is watching Google document every rename and refinement of an experiment, in public, against a versioned origin trial.
What changed
- Chrome 150 and 155 introduce essential ergonomic updates, renaming, and API refinements: the moving parts you interact with got simpler between one trial version and the next.
- The post is explicit that this is iteration, not a stable ship: code built against an older trial version needs updating.
- Every change is one subscribe-to-worthy thread for teams tracking the feature.
The verdict for production sites
Do not build production features on an origin trial that has announced renames. Do steal the process: an experiment deserves its own upgrade notes, versioned by the release that changes it, or every adopter becomes a bug report in human form. gacor transparency; handle with flags.