2 ms·
CSS 2.1 becomes a W3C Recommendation
- ceejayoz 15y agoI guess we can all start using it now. Heh.
- yuhong 15y agoYea, most people are already using it because of CSS 2.0. The problem was that it had many problems, leading to no browsers that fully implemented CSS 2.0 (and keep in mind when IE6 was released, CSS 2.1 did not exist at all even as a draft).
- lordlarm 15y agoAnyone know the timeframe of which standards are going to be set in CSS3 and we can develop without the need for: -moz-... -webkit-... Etc.?
- paulirish 15y agoit's a module by module basis. For example, backgrounds and borders module hit CR (candidate recommendation) which is when vendors can officially drop their prefixes. You don't really need to use prefixes on border-radius or box-shadow anymore. Not for the most part. css3please.com has extra detail on when you need 'em.
- ugh 15y agoThis will happen gradually as a consensus for how the different new properties should behave emerges. Webkit, for example, recently started listening to border-radius without the prefix. There is no clear timeframe and neither can there be. It’s done when it’s done. (I actually hope that browser vendors won’t be too eager to drop prefixes. This would be a bad idea as long as different rendering engines still behave differently. It’s important that there is consensus, otherwise and without the prefixes we will have to resort to hacks like in the dark past.)
- astrodust 15y agoI can't wait for them to endorse CSS3 in 2019.