3 ms·
The arguments sound good, and there is obviously a lot of frustration that led to this, but: Will this mean that new features will take even longer to come out
by Illniyar 11y ago
The arguments sound good, and there is obviously a lot of frustration that led to this, but:
Will this mean that new features will take even longer to come out?
What about features that aren't standardized, or in very early stages, heck, safari has lots of css properties that aren't even close to being implemented (such as -webkit-overflow-scrolling ).
Taking this route, either a browser can't implement something that isn't standardized, or when it is standardized, it'll be incompatible with a future standard (think flexbox and it's thousand implementations).
We could end up worse, to prevent sites from breaking, the standards body will choose a different property name for things browsers implemented before standardization, which means we'll get the same effect as vendor-prefixes but without readily visible names.
- notatoad 11y agoYou can look at chrome's behaviour for the last couple of years to get an idea of how this might play out. Basically, the big browser vendors are the new standards bodies, and the w3c/whatwg plays catch up with what the browsers are implementing. If three browsers all agree to implement something, it gets implemented without waiting to hear what a standards organization says, and then it gets documented in a standard later on.