5 ms·
I don't think you understand why the prefixes are there. CSS was designed in a way that things should either work or not. There shouldn't be different ways to i
by tvdw 14y ago
I don't think you understand why the prefixes are there. CSS was designed in a way that things should either work or not. There shouldn't be different ways to interpret a property. With browsers battling over several syntaxes for CSS3 implementation, the last thing we want is to have webdevs build a separate stylesheet for every browser out there, because (for example) "transform:" works different on Firefox 3 than on Firefox 4, and Chrome's implementation is also different. The prefixes help a lot here: you can group all these different stylesheets into one by using the prefixes, and once the standards are finalized they'll just use one syntax that can't be interpreted any other way.
- TazeTSchnitzel 14y agoCSS parsing rules mean it doesn't matter. You can simply specify a property with several syntaxes, and browsers ignore the ones they don't recognise.
- daeken 14y agoLet's say that you have a property that takes in two color parameters, crazy-coloring. Webkit implements crazy-coloring: bgcolor fgcolor; Gecko implements crazy-coloring: fgcolor bgcolor;. How do you propose we differentiate these and know what the designer meant? That's why we have prefixes, until it's standardized.
- TazeTSchnitzel 14y agoUsually we don't end up with cases that are that drastically different. And in that case, now only Webkit, Gecko, and maybe Trident and Presto are considered. Other, less popular rendering engines are rarely included in the set of prefixed properties, excluding them from the ability to use new features.
- daleharvey 14y agoindexedDB specifically had very different behaviour in webkit and firefox, it still does afaik
- TazeTSchnitzel 14y agoThere's also different behaviour across versions. Prefixes don't help.