Wisnu Mulya15,578 Points
Why don't the browsers' makers just release the un-prefixed CSS features?
I'm just wondering of the reason why the browsers' makers not yet release the un-prefixed version of many CSS features like Flexbox or Multi-Column. If they're able to launch the browsers' versions that support the prefixed syntax (like -webkit-, -o-, -moz-), why don't just launch the browsers' versions that support the un-prefixed syntax already?
Chris Shaw26,640 Points
The reason most CSS3 features are prefixed is because vendors are still testing and developing them, recently the Chrome dev team released an update to Chrome 36 which saw the
transform properties remove the
-webkit prefix after 35 versions so they don't go away easily until the vendor is satisfied that their implementation matches that of the W3C specification.
As for features such as Flexbox they won't be un-prefiexed for a long time to come as the specification still isn't complete so vendors are implementing it different ways which is causing inconsistencies in certain circumstances.
Kang-Kyu Lee49,730 Points
Like the teacher said, we see here http://caniuse.com/ things are changing and slowly all the browsers getting up to date when a new thing comes out. (I don't know how old something like 'CSS transform' is by the way.) And also I guess the users do not usually move very fast. We don't know anybody wants to enter but didn't update their browsers, Like I heard we better build it more for all of the cases, all the browsers. Like we try an app for all the screen sizes here or else http://quirktools.com/screenfly/
Philip Cox14,818 Points
It takes a long time for the W3C to release a feature as a new specification.