CSS Prefixes – The current battle
So, don’t tell anyone, but over the past month, in the web pages I was creating, I kind of . . . . wasn’t very consistent with my CSS coding.
Sometimes I would use the -webkit- prefix, but most times I would just skip the thing and just write box-shadow: 1px 2px 4px #414042 (or whatever) about twelve lines below a -webkit-box-shadow declaration. I’m sure it’s not a big deal. I mean, the site worked. But it bothered me that I even did things like that. Because, why should I even have to use the prefix?
Apparently I’m not the only one wondering about the prefix bit. But the issue isn’t, why do I have to use it, it’s more like, why is everyone just going to conform to the -webkit- bit? I see it as a step backwards. Like, sure there are things like -o-border-radius and -webkit-border-radius and -moz-border-radius and stuff, but there’s also the plain old, non-prefixed, border-radius. So why bother with all the others?!
So, because Mozilla is deciding to start supporting the -webkit- prefix, what’s going to happen to the poor non-prefixed CSS tags? What’s the point of having a big CSS Worldwide Consortium? I am not a fan. And neither is a writer of this article from A List Apart. The idea of having standards is to make, say, web development easier for everyone, because I sure don’t want to have to make a website five times.
I guess my point is, browser developers, don’t give in to the fact that Apple uses the Webkit engine and therefore must be supported by everyone. And developers, stop using -webkit- CSS properties if you’re building for the general web.
Can’t we all just get along?