3 ms·
It's just nomenclature; CSS3 will eventually just become "CSS" and each module will move forward on its own. And they're really just codifying what was already
by mnutt 14y ago
It's just nomenclature; CSS3 will eventually just become "CSS" and each module will move forward on its own. And they're really just codifying what was already happening: browsers never jumped from CSS1 to CSS2 or CSS2 to CSS3; they just added support bit by bit.
- pbhjpbhj 14y ago>they just added support bit by bit // I imagine that, in part at least, is because the standards have taken so long to be codified. We've been calling it CSS3 and it's been implemented gradually in browsers but it's still a working document and not a finished standard (and now it seems never will be). The pace of required changed for the needs of web page production and rendering is faster than the pace of the standards confirmation. If this is just to address this issue then why not have "selectors 3", or whatever, as a part of a point release.