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

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

From: fantasai <fantasai.lists@inkedblade.net>
Date: Wed, 25 Jan 2012 13:25:49 -0800
Message-ID: <4F20735D.8080301@inkedblade.net>
To: Vincent Hardy <vhardy@adobe.com>
CC: "www-style@w3.org" <www-style@w3.org>
On 01/25/2012 11:31 AM, Vincent Hardy wrote:
> fantasai wrote:
>>
>>    # 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?

Both specs are wrong, given the existence of 'box-decoration-break'.

~fantasai
Received on Wednesday, 25 January 2012 21:26:26 GMT

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