W3C home > Mailing lists > Public > www-style@w3.org > May 2011

[css3-regions] New CSS Regions editor draft

From: Vincent Hardy <vhardy@adobe.com>
Date: Mon, 30 May 2011 17:09:04 -0700
To: W3C style mailing list <www-style@w3.org>
Message-ID: <69696D1D-9CD4-4B9A-ADCA-D4D01A62CED9@adobe.com>

I have published a new version of the CSS Regions working draft. Please find the log of changes below.

The new draft is dated May 29th:

Kind regards,
Vincent Hardy.

- Made flow property type a <string> & added issue.

- Added issue about content-order being a <float> and not an <integer>

- Added issue about duplicating content into a flow instead of moving
to a flow (http://lists.w3.org/Archives/Public/www-style/2011May/0521.html)

- Added a region-overflow property

region-overflow: break | auto
where break would not position elements that do not fit and auto would
break if the region is not the last one and overflow if it is the

- DID NOT ADD. Add an example with 'projection' media (because that does not seem to belong to the spec.)


- content syntax:

content: from-flow(); // To clarify that from is bound to a 'flow' property

- region styling:

Limit to ::region-lines and include issue about element fitting fully in
region + issue about right list of properties.


Added issue about selecting only elements that fall fully into the region:

- Use @region instead of @region-style:


- content: from-flow() applies to block level elements.


Also applies to non-replace block elements:


- Do not provide content balancing


- Removed flexbox example:


- Modified CSSOM View

Element.regionOverflow = overflow | fit | empty
Issue about 'onlayoutchanged'
Issue about locating a region from an flow element.

- Use intrinsic width of 0 for region content.


- Breaks.

Added wording about where breaks may happen and reference the Paged Media


- Added reference to first-line pseudo-element and list of properties

- Some additional restyling.

- Removed issue 12 about 'range' selection since this is no longer
relevant with the proposal to only match elements that are fully in the

- Added note about concern over underspecification of the first-line


- CSSOM View: renamed ContentFlow to NamedFlow

- Removed issue on accessing multiple clientRects on Element since
there is already an interface for that:

- Added comment that floats in the region flow impact the content flowing into the region.

Comment from implementor Alex Chiculita.

- Added issue about doing capture/bubble through a region element.

Comment from implementor Alex Chiculita.

All Emails with [css3-regions] threads.

[css3-regions] OM for region content overflow

Proposed to use:
Element.regionOverflow = overflow | fit | empty

in http://lists.w3.org/Archives/Public/www-style/2011May/0508.html (last
thread message).

[css3-regions] pagination and inline elements


Explained that there are use cases for a chain of fixed-size container
ending with a flexible container. No changes to the spec.

[css3-regions][css3-content] Explicit/Implicit, Named/Anonymous Regions


Added issue raised by Fantasai about underspecification of ::first-line.
Added an issue about copying content to a flow instead of moving it to a
flow (raised by Christoph).

[css3-regions] region breaks


Added issue about unification of region/page/column breaks.

[css3-regions] region sthyling (Feedback on regions document)


Proposed the @region & ::region-lines combination.

[[css3-regions] Feedback on regions document

- Settled on region styling alternate proposal (@region + ::region-lines)
- Agreed to not bind a flow and a region directly (as in #flow { position:
into(region); }) 
- Agreed to keep regions that are document elements
- Agreed on intrinsic width=0 for regions.

[css3-regions] more feedback


- removed issue on balancing content.
- removed issue on generating additional regions automatically.
- removed issue on adding features for 'flexible' flow elements.
Received on Tuesday, 31 May 2011 00:09:35 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:38:46 UTC