3 ms·
Apple's success with WebKit, combined with their success in advancing browser technologies, is partially responsible. To explain... Their use of vendor prefixe
by eyelidlessness 10y ago
Apple's success with WebKit, combined with their success in advancing browser technologies, is partially responsible. To explain...
Their use of vendor prefixes was proscribed by the standards (and may well still be). After years of stagnation in browser technologies, and demand from content producers and developers for advancement, vendor prefixes were seen as a way to vet real-world usage of new standards before they were formalized.
But because standardization was still quite slow, and because vendors (all of them!) were slow to remove prefixes, and because non-WebKit vendors lagged behind WebKit in features (for a while), the proliferation of `-webkit-*` was inevitable.
Today's rejection of vendor prefixes is a reflection of that intersection of problems. They were maybe never a great solution to the problem that preceded them, but they are no longer suitable and that's just fine.
I'd prefer Firefox (and every other vendor) simply disabled handling for prefixes entirely. But there is a ton of content that will never be updated again, and would break. Without some kind of versioning, that's untenable.
And we already saw what happened when Mozilla tried to introduce versioning. (It was never supported by other vendors, and therefore never used by developers.)