3 ms·
no, to become a standard at least one other browser vendor would have to at least signal an intent to implement it.
by notatoad 3y ago
no, to become a standard at least one other browser vendor would have to at least signal an intent to implement it.
- troupo 3y agoNo. To actually become a standard it needs at least two inependent implementations. But it's interesting that you wrote what you wrote. Because that's exactly what Chrome is doing: it's announcing an intent to implement, and then enables whatever they intend by default. Oh, they do pretend to ask other vendors about their position, but ship anyway. And then use web.dev to pretend it's a standard.