Forum Moderators: not2easy
It seems the Opera Antitrust complaint with the EU [opera.com], in which it "Urges Microsoft to give consumers a genuine choice of standards—compliant Web browsers" has caused some deep seated fallout about the actual CSS Working Group themselves, (the bigger issue may be threat to the authority of the W3C itself, but that's another topic)
As to whether the Opera complaint is justified at this time, or is just the spark to light the new flame.. I'm not sure, and I understand there's more to it than meets the public eye. Anyway the complaint is not the reason for this post. The reason for this post is more the 'can of worms' it seems to have opened for the CSS Working Group [w3.org]
Unfortunately, the period of IE's stagnation (pre IE7) coincided with a stalemate whereby MS wouldn't do and the W3C didn't do any more to further the progress of bringing existing CSS2.1 features to a specification. I can understand the frustrations from the Working Group on this one there's not much they can do except keep recommending. However this was probably the best time to push it and close the 2.1 chapter, users could already cope with serving IE plainer sites via Conditional Comments!
Perhaps it was the sheer speed that things were being implemented which meant the W3C couldn't keep up or perhaps they were waiting (or had to wait?) to see what MS did. Either way it caused progression of both development of CSS and the existing standards to slow to a snails pace, neither one going anywhere really.
The W3C have always maintained that manufacturer allegiances are to be left at the door when preparing the recommendations of the CSS Working Group - were they really? or did the W3C just get bogged down in double-speak allowing the time to slip past and the manufacturers time to develop according to their own standards again
Are the recent calls for a shake up in the formation of the CSS Working Group justified?
Andy Clarke (who is an invited expert on the CSS-WG) writes in his post entitled "CSS Unworking Group":
I propose that instead of actively participating in the development of new CSS standards as part of the CSS Working Group, that browser vendors instead form a Technical Advisory Group that is attached to the new CSS Working Group. Their role should be to advise on the technical limitations or requirements of the proposals that the new group creates. Along with the formation of this new group, new processes for communication and participation are needed, plus a clear strategy, with dates attached for the delivery of the new standards.
or should the responsibility for CSS move to WhatWG "until the CSS-WG sort themselves out"...as Ian Hickson hints at:
One way to address this would be for the WHATWG to start a "subproject" to address CSS, while we wait for the W3C CSS group to learn from the W3C HTML group and become open. The biggest problem would be finding editors who would be willing and capable of doing the incredible work of rewriting CSS from scratch.
I sure don't like the second one.. moving now, and to a "subproject" at that, would just shift the perceived problems back further, as for rewriting from scratch well that's just plain nonsense.. everyone is allowed to learn from their mistakes, MS appear to have and I'm sure the CSS-WG volunteers can too.
Another solution to the lack of progress of CSS is that we need to let the browsers return to their wars so they can get on with pushing their proprietary features while W3C standardizes the ones that are adopted early. Whether you agree with "Browser Wars" being the only way to advance development and standardization or not it obviously can't take place until the Browsers and the CSS-Working Group sort themselves out and learn to work together transparently! I see a place for everyone in this little scenario but all involved need some changes in attitude to achieve the best all round solution.
anyhow.. it would be a crying shame if the work of the last 10 years was wasted. Users and Manufacturers both seem to look upon the recommendations as their standards already (ACID2 anyone?) so why throw the baby out with the bath water by calling for disbandment of the Working Group when the work they've done is already looked upon as our present CSS Standards.. let's move forward not back.
-Suzy
