This page started from the initial CSS Regions working draft.

References:

• CSS Regions working draft
• CSS Regions editor draft
• Archived Changelogs

Code Samples

regions-nightly-samples.zip

• height:auto processing model
• region styling alternate syntax
• CSS Object Model for CSS Regions
• user event handling

Use cases

• Complex Layout Example
• CSS Regions Use Cases
• CSS Regions Use Cases from Print Sources
• Separating regions markup from content markup
• Scope Issues

Each of the Regions tests will have metadata that points back one or more ids used in the Regions spec. These ids may be heading or dfn elements, or they may be ids added at the paragraph or sentence level to indicate a specific conformance requirement that must be tested. We should be able to scan the spec for ids (ignoring non-testable ids) and find at least one test for every testable id in the spec.

Whether an id is testable can be determined by scanning the spec and ignoring any id in elements with these class attributes: example, note, toc, no-toc or informative. The “informative” class attribute is new, and can be added around non-normative sections of the spec, or any id that's found not to correspond to a conformance requirement.

It was decided during this conference call (http://krijnhoetmer.nl/irc-logs/css/20110824) to create a separate spec. for issues that are common to regions, multi-column and page media. List of issues raised by CSS regions editors:

• Which elements break along container (column, page, region) boundary and which do not?

• How do breaks work together, in particular in nested scenarios?

• Behavior of fragmented floats: does each 'float' fragment behave as a regular float in its container?

• How does the transform property (and transform-origin) work for content split across multiple containers?

This page used to track resolutions and issues, but that was discontinued. The old tracking data can be found on these archive pages:

Archived Resolutions

Archived Issues