[jrochkind1]

Every browser has never implemented exactly the same things in exactly the same ways, and never will. There will always, at least, be bugs.

A "de facto standard" of "what browsers implement" is no standard at all. This is why standards matter. "What the actually existing software implements" is what you have when you _don't have standards_.

The vendor-dominated, standard-changes-every-day WHATWG "living standard" is relevant to the situation here, I think, even if you'd rather it not be. If it's a living standard that's always changing, and it's specifically changing based on _what software does_... then Chrome doing something seems like as much of a standard as anything. It may or may not be added to the standard the next day, but the standard seems to encourage people to use things that aren't in it yet.

The WHATWG process, if I understand it right, specifically requires (at least) two browser vendors to implement a thing _before_ it's added to the standard. Yes, two is more than one. But not a lot more. :)

[alwillis]

Every browser has never implemented exactly the same things in exactly the same ways, and never will.

Igalia implemented CSS Grid for both Blink and WebKit: https://blogs.igalia.com/mrego/2017/03/16/css-grid-layout-is...

And remember, Blink is a fork of WebKit, so they're not very different. So it can be done and we need more of this.

They're also working on some other stuff for Apple and Google. Never say never.