Since the idea of CSS2.2 was raised, there’s been some discussion as to what it should encompass, who should be responsible for the spec, and what it should be called; here’s what I think:
First, it doesn’t matter what it’s called. Whether it’s referred to as CSS2.2, CSS2.1+, CSS3 Interim, or whatever, makes no difference. It doesn’t need to have a name at all; the important thing is that we have it.
Second, it doesn’t need to be an official recommendation from the W3C; in fact, it may be easier if it’s not. The optimal solution would be communication between developers and browser manufacturers, and – crucially – between the browser manufacturers themselves. What’s needed is an agreement as to which features are implemented, and to make sure those features are implemented in the same way; a de facto standard.
Finally, what feature should it include? For me, it has to be the elements which have already been implemented and tested in at least one browser for an amount of time sufficient for developers to have used them.
The most-requested feature is multiple background images; if you’re going to have that, background clip, origin and size would be wanted too. Border images would also be useful, as would an agreement on implementation of border radius.
Opacity, and with it RGBA and HSLA, box shadow, and text shadow would round off the decorative declarations.
Even if those few could be agreed on, a lot of workarounds could be avoided.
I would have said that multi-column layouts were less urgent, but as they are already part of the Gecko engine and about to be introduced in Safari 3, it seems that that should be part of the standard. Media queries would be pretty necessary as we move into the mobile era, too.
Nothing I’ve mentioned above would be unrealistic; most have already been implemented in at least two current or imminent browsers. As they are available, why are we being kept waiting before we can use them? Think of all the extraneous markup we could be freeing ourselves from!
Come on, browser makers: open up lines of communication and get talking to one another; float the ideas on your company blogs, see what your readers have to say. There’s a whole big community of developers who love to download nightly builds and test new features, and are hungry to improve their pages.
You can skip to the end and leave a response.
What, no “Substring matching attribute selectors”?
In fact we are using floats for our layouts today. Floats are never be intended to create three or four column layouts. Learning it and fix around Browser Bugs is very hard.
So please implement useable CSS properties for Multi Column Layouts soon, there are a few modules in progress @ w3c why is no one of this ready for fighting against floats as a site Layout module.
Opacity/rgba/hsla is already at the Candidate Rec stage in the CSS3 Color module. text-shadow is in CSS2 Rec, so it’s effectively in CR. The rest of the features you’re requesting are in CSS3 Backgrounds and Borders, so all we really need is to push that into CR. It needs another round or two of editing and reviewing first, but unless some major problems are found it should be possible to get it to Last Call at least by the end of the year (if we prioritize appropriately, which I hope we will). Comments on what looks good and what could be improved would be very helpful. The discussion in http://www.css3.info/border-radius-apple-vs-mozilla/ about border-radius had a lot of great points.
@mira Multi-col won’t solve layouts with different panels, it flows continuous text into multiple columns. The CSS3 Advanced Layout module is intending to address layout columns. We agree floats are a pain. They were never designed to do column layouts, and neither was absolute positioning (which is also a pain). Coarse layout is currently a gaping hole in CSS. :(
Css 2,2 is the standard we use for years, the most recent standard for development of xhtml 1.0 strict target usability and accessibility for website development. The css3 has been developed for many years and its really tiring to wait for a new standard but as well as waiting it is very interesting to test and work with cross browser solutions and at moo tools i have tried out many of these css3 technical solutions…
I wish to also publish many templates and resources at my website… soon but im so busy at the office… maybe one day i will share my solutions also…
[…] a lot of heavy flak last year for being slow, cumbersome, bureaucratic, etc; there were calls for a CSS2.2 (which I seconded) which rounded up all the existing implemented features, and for the CSS Working Group to be […]