The arguments sound good, and there is obviously a lot of frustration that led to this, but:<p>Will this mean that new features will take even longer to come out?
What about features that aren&#x27;t standardized, or in very early stages, heck, safari has lots of css properties that aren&#x27;t even close to being implemented (such as -webkit-overflow-scrolling ).<p>Taking this route, either a browser can&#x27;t implement something that isn&#x27;t standardized, or when it is standardized, it&#x27;ll be incompatible with a future standard (think flexbox and it&#x27;s thousand implementations).<p>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&#x27;ll get the same effect as vendor-prefixes but without readily visible names.