3 ms·
I couldn't agree more. I can't imagine how many hours of clean-up it will take for all the webmasters to clean vendor prefixed properties out of their CSS files
by CWIZO 17y ago
I couldn't agree more. I can't imagine how many hours of clean-up it will take for all the webmasters to clean vendor prefixed properties out of their CSS files once browsers drop them.
- roam 17y agoI think ppk is wrong here. Completely wrong. As mentioned in the comments of the article, this would mean the first to implement a new feature would be able to define how it works. Not a good idea. We need some form of consensus. And also mentioned: some things do change. The definitions of border-radius for Gecko and Webkit are not the same at all.
- ionfish 17y agoSome code I found myself writing recently: var fader = Faders.Default, test = document.createElement('div'); 'o moz webkit'.split(' ').forEach(function(prefix) { test.style.cssText = '-' + prefix + '-transition-property: opacity;'; prefix = prefix === 'moz' ? 'Moz' : prefix; if (typeof test.style[prefix + 'TransitionProperty'] !== 'undefined') { fader = Faders.Transition; fader.use(prefix); } }); Would really rather not have to do something like that again.
- edd 17y agoYou don't have to clean up. If they are no longer being obeyed they will just be ignored. You would only remove them if you are redesigning, in which case you remove them as you go. Just make sure if you are currently adding in vendor prefix stuff you add a general case for everyone else now. Future and backwards compatible.