4 ms·
Why doesn't the standards body ask webkit to deprecate and begin to phase out any -webkit-* CSS selectors which have been fully standardized? That seems like an
by eslaught 15y ago
Why doesn't the standards body ask webkit to deprecate and begin to phase out any -webkit-* CSS selectors which have been fully standardized? That seems like an effective way to force people to use the standards once they actually exist.
Complaining about people using -webkit-* before the standards exist is obviously unreasonable, considering the implications of populating the global namespace with conflicting versions of the same feature.
- deleted 15y ago[deleted]
- ootachi 15y agoBringing up racism, sexism, and homophobia in a discussion of Web standards is a little bit extreme, don't you think?
- bzbarsky 15y agoThe standards body has asked WebKit to do that, in fact. Apple flat-our refused to ever remove -webkit prefixes that they have once shipped. Note that no one is complaining about the mere existence of the prefixes; the problem is: 1) The way they're being used by web developers. 2) The fact that some of these properties are not standards-track, with Apple actively refusing to allow them to be standardized.