Comment by troupo

> It is the decision of the other vendors to not implement the standards

A scribble on a napkin does not a standard make.

A feature released in a single browser engine without support, consent, and against objections of other browser vendors does not a standard make.

Just because Chrome ships something does not make whatever they ship a standard.

> The documentations and specifications are available for free.

That's how Chrome abuses its position and relies on gullible devs to assume that just because something is documented it becomes a standard the moment it's shipped in Chrome.

That's not how standards work.