Seems like you have some pretty strong ranty bias there.

AFAICT, this is a web standard and expected to get buy in from Safari and Firefox before shipping to users. For now it's an experiment you have to specifically enable with flags. No different than any other browser that runs experiments

Here's one from from Apple from 2017

https://webkit.org/blog/7504/webgpu-prototype-and-demos/

Here's another from last year

https://webkit.org/blog/17118/a-step-into-the-spatial-web-th...

▲

JimDabell 2 hours ago | parent | next [-]

> AFAICT, this is a web standard and expected to get buy in from Safari and Firefox before shipping to users.

If it hasn’t already got buy in then it isn’t a web standard, it’s just a Google proposal. Something isn’t automatically a web standard just because Google thinks it’s a good idea.

Here are Mozilla and WebKit positions on this:

> This proposal attempts to solve multiple problems with a single solution. We (Mozilla) recognize the motivation for solving some of the problems, but believe that this is not the right solution to each problem, or in some case a step in the wrong direction.

— https://github.com/mozilla/standards-positions/issues/1076

— https://github.com/WebKit/standards-positions/issues/630

As far as I can see, nobody outside of Google has committed to implementing this.

	▲	troupo 2 hours ago \| parent [-]
		From the discussion linked in the Webkit repo: --- start quote --- Philip: First, google slides is written in svg, so that won't change with this. But google docs is using canvas, so they might be a candidate. … they might want to integrate this peicemeal, this API allows them to start to adopt the feature slowly, --- end quote --- This reads to me like "Google Docs decided to go with canvas sometime ago [1], found it to be too hard, so pushed Chrome to have a way to support HTML in Canvas. The rest is just post-hoc justifications" [1] https://workspaceupdates.googleblog.com/2021/05/Google-Docs-...

▲

troupo 2 hours ago | parent | prev [-]

> his is a web standard and expected to get buy in from Safari and Firefox before shipping to users.

1. It's not a standard. It's a scribble on a napkin in a working group's repo: https://github.com/WICG/html-in-canvas Created and edited by people from Google.

2. Chrome continuously ships "standards" like this that they create with no buy in and against any and all opposition.

3. Neither of your links have any relation to HTML in Canvas.