Extensions to the CSS Object Model

The CSS Object Model is now almost eleven years old. All Web authors know it’s only partially implemented and rarely interoperably implemented. There is now an ongoing effort to stabilize the most mature bits of the specification.

Thirteen years ago, after the release of CSS 2, we pinged the Web authors’ community to gather a List of suggested extensions to CSS. It’s now time to do the same for the CSS Object Model. If you have suggestions for the future of the CSS Object Model, please send a mail to www-style@w3.org or myself, with a subject line starting with [cssom]. Please make sure to add real-world use case(s) to your suggestions.

All suggestions will be added to a public page. Your name and email address will not appear.

Thanks !

Daniel Glazman
CSS Working Group, Co-chairman

2 thoughts on “Extensions to the CSS Object Model

  1. I have a good idea for providing a new feature to CSS, and have a rough draft that outlines how it might appear in CSS. How may I submit this to the CSS working group for consideration and discussion, so that it might be included in a future version of CSS, and perhaps in SVG? I think this idea is something that designers would really appreciate, because it makes code maintenance easier. The core idea is simple and could potentially be applied to other concepts. So I’d like to have the group consider it.

    The only thing I’ve really found is the suggestion to join one of the public mailing lists for discussion. I’ve just seen the new item on community and business groups to develop web technologies more rapidly.

    But — Is there a more appropriate way for me as an individual to submit something to the CSS working group, and what format and requirements should be met?

    Thanks very much in advance.

  2. Of cause it is quite important to be up-to-date and use innovations, but on my opinion there is no huge difference for 90% of developers which version of CSS do they use, CSS2 or CSS3. More important moment is how browsers will interpret the code. I hope that in next years we will not have not look for cross – browser solutions, but just write code and forget about this problem. I faced with it while developing my web site and I really worry how the web site will look in next versions of browsers.

Comments are closed.