W3C home > Mailing lists > Public > www-style@w3.org > January 2012

Re: [css3-regions] definitions of 'break-*'

From: Vincent Hardy <vhardy@adobe.com>
Date: Wed, 25 Jan 2012 11:31:06 -0800
To: fantasai <fantasai.lists@inkedblade.net>
CC: "www-style@w3.org" <www-style@w3.org>
Message-ID: <666E6CFC-4A64-4ED9-8576-14FC1A0E3F01@adobe.com>
Hi Fantasai,

On Dec 26, 2011, at 7:41 PM, fantasai wrote:

>   # 4.3 Region flow break properties: 'break-before', 'break-after', 'break-inside'
> 
> CSS Regions should only be defining the new values, not the old values, of these
> properties. So the first <dl> should be removed.

[vh] This whole section followed the multi-column spec. for its structure and text:

http://dev.w3.org/csswg//css3-multicol/Overview.html#column-breaks

which says that values auto/always/avoid/left/right are normatively defined in CSS21 but does include their definition. While I followed that pattern, I agree with you that it is better to only define the new value. I made the change.

> 
>   # When a break splits a box, the box's margins, borders, and padding have no visual
>   # effect where the split occurs. However, the margin immediately after a forced
>   # page/column/region break will be preserved. A forced page/column/region break is
>   # a break that does not occur naturally.
> 
> This paragraph is inaccurate and should be replaced by a paragraph stating simply that
> breaking across regions is treated exactly the same as breaking across pages.
> 

[vh] I am happy to remove that if that is the right thing to do. It would help to understand why the paragraph is incorrect. The text is modeled after:

http://dev.w3.org/csswg//css3-multicol/Overview.html#column-breaks

which says:

"When a page or column break splits a box, the box's margins, borders, and padding have no visual effect where the split occurs. However, the margin immediately after a forced page/column break will be preserved. A forced page/column break is a break that does not occur naturally."

Is the text in regions saying something inaccurate compared to the multi-column spec? If so, can you point out what the issue specific to regions? Or is the issue in both regions and multi-column?

>   # Note: When the ‘avoid’ value is used, regions may overflow. In that case the
>   # ‘overflow’ property specified on the region element should be used to determine
>   # how to render the overflow.
> 
> This is not how the 'avoid' value of 'break-*' normally behaves: it indicates that
> a break should be avoided in this content, not that it should be forbidden. If the
> content would otherwise overflow, it breaks instead. IMO regions should not behave
> any differently from columns or pages in this respect.

[vh] Actually, the point of this text was not to change the behavior of break-*: avoid but to mention that in case content overflows the region box, the visibility of the overflowing content is controlled by the 'overflow' property. But since this is covered by a note in the region-overflow property description, I removed this altogether.

All changes from this feedback at http://dev.w3.org/cvsweb/~checkout~/csswg/css3-regions/Overview.html?rev=1.40;content-type=text%2Fhtml

Thanks!
-v
Received on Wednesday, 25 January 2012 19:31:47 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:49 GMT