W3C Working Draft, 23 May 2001
This version: http://www.w3.org/TR/2001/WD-css3-roadmap-20010523 Latest version: http://www.w3.org/TR/css3-roadmap Previous version: http://www.w3.org/TR/2001/WD-css3-roadmap-20010406 Editors: Eric A. Meyer Bert Bos (W3C)
Copyright ©2001 W3C® (MIT, INRIA, Keio), All Rights Reserved. W3C liability, trademark, document use and softwarelicensing rules apply.
The members of the CSS&FP Working Group have decided to modularize the CSS specification. This modularization will help to clarify the relationships between the different parts of the specification, and reduce the size of the complete document. It will also allow us to build specific tests on a per module basis and will help implementors in deciding which portions ofCSS to support. Furthermore, the modular nature of the specification will make it possible for individual modules to be updated as needed, thus allowing for a more flexible and timely evolution of the specification as a whole. This document lists all the modules to be contained in the future CSS3 specification.
Status of this document
This is an official introduction, issued by the CSS WorkingGroup, which details the modularization of the CSS3 specification and the CSS test suite. This document should be considered to be informative, not normative. See the Style overview pages for more information on W3C's work on style sheets, including CSS. This is a public W3C Working Draft for review by W3C members and other interested parties. As a draft document, it may be updated, replaced, orobsoleted by other documents at any time. It is inappropriate to use W3C Working Drafts as reference material or to cite them as other than "work in progress." A list of current W3C Recommendations and other technical documents including Working Drafts and Notes can be found at http://www.w3.org/TR. Please send comments to the email@example.com mailing list (see how to subscribe) or to the editor.Table of contents
1. Why Modules? 2. Module Overview 3. Module Descriptions and Related Information 3.1. Introduction 3.2. Syntax / grammar 3.3. Selectors 3.4. Values & units 3.5. Value assignment / cascade / inheritance 3.6. Box model / vertical 3.7. Positioning 3.8. Color / gamma / color profiles 3.9. Colors and Backgrounds 3.10. Line box model 3.11. Text 3.12. Fonts 3.13. Ruby 3.14.Generated content / markers 3.15. Replaced content 3.16. Paged media 3.17. User interface
3.18. WebFonts 3.19. ACSS 3.20. SMIL 3.21. Tables 3.22. Columns 3.23. SVG 3.24. Math 3.25. BECSS 3.26. Media queries 3.27. Test Suite 4. Appendices 5. Module template
1. Why Modules?
As the popularity of CSS grows, so does interest in making additions to the specification. Rather than attempting to shovedozens of updates into a single monolithic specification, it will be much easier and more efficient to be able to update individual pieces of the specification. Modules will enable CSS to be updated in a more timely and precise fashion, thus allowing for a more flexible and timely evolution of the specification as a whole. For resource constrained devices, it may be impractical to support all of CSS.For example, an aural browser may be concerned only with aural styles, whereas a visual browser may care nothing for aural styles. In such cases, a user agent may implement a subset of CSS. Subsets of CSS are limited to combining selected CSS modules, and once a module has been chosen, all of its features must be supported.
2. Module Overview
All modules contain a "Conformance: Requirementsand Recommendations" section. Any module whose table row is backed with green is considered part of the "CSS Core." The listed deadlines (backed in red) represent the time at which a module should be ready for Working Draft publication. There are also columns which indicate a module's participation in each of three "profiles": HTML Basic, CSS3, and SVG. A module without any indicated module...