Firefox Will Support Non-Standard CSS For WebKit Compatibility (theregister.co.uk)

RoccamOccam writes: Mozilla developers have discussed a plan to implement support for a subset of non-standard CSS prefixes used in WebKit. Mozilla developer Daniel Holbert says: "A good chunk of the web today (and particularly the mobile web) effectively relies on -webkit prefixed CSS properties & features. We wish we lived in a world where web content always included standards-based fallback (or at least multiple-vendor-prefixed fallback), but alas, we do not live in that world. To be successful at rendering the web as it exists, we need to add support for a list of frequently-used -webkit prefixed CSS properties & features."

Comments

Re:Safari really is the new IE

[Anonymous Coward]

It isn't so much Safari, more Chrome.

And it isn't even Webkit devs fault, it is the shit standards committee for being too slow at making things standards and shit developers for using experimental code.
But the biggest part of the issue is web browser vendors having experimental things behind a prefix in the first place!
It should only ever work if someone enabled a flag in the advanced settings, like originally planned. (about half of the experimental code is behind a flag, the rest completely open)

Fact: most developers are awful at their work and cannot make simple, informed and sensible decisions.
People go on about how children can't make informed decisions yet there are billions of adults that regularly make stupid decisions every damn day.
Last I remember when I was a kid, I decided my entire future down to the T, and multiple backups in case I never got in to said industries for whatever reason. (I know, I know, I am a minority, but I point you back to the start of this paragraph, most people suck all kinds of ass.)