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

[css3-break] Consuming Height at Breaks

From: fantasai <fantasai.lists@inkedblade.net>
Date: Tue, 07 Aug 2012 16:55:49 -0700
Message-ID: <5021AB05.8000203@inkedblade.net>
To: "www-style@w3.org" <www-style@w3.org>
 From the minutes:

>    fantasai: Proposal: first, do you use up specified height for the gap?
>              The answer is "no, never".
>    fantasai: Second, when do you draw the background/borders in the gap?
>              Answer is, in the fixed height, no. In auto height, yes.
>    TabAtkins: the value of this is that it preserves the invariant that
>               dbaron wanted to preserve, while looking good for both for
>               the common cases.
>    RESOLVED: Accept the CSS3 Break proposal as stated in the minutes.

I'm interpreting "specified height" here as "specified <length> or <percentage>",
since we have a lot of keywords that auto-calculate the height.

Here's the spec text so far:
   # If the box is inline or is a block-level box with its extent specified as a
   # <length> or <percentage>, then the fragmented content box ends at the break
   # point and resumes after the break.
   # Otherwise, the content box extends to fill the remaining fragmentainer extent
   # (leaving room for any margins/borders/padding applied by
   # ''box-decoration-break: clone'').
   # In all cases, any extra extent contributed by fragmenting the box
   # (i.e. the distance from the break point to the edge of the fragmentainer)
   # does not consume any specified <length> or <percentage> extent.


We didn't discuss non-block-level boxes. This text puts inline elements into
the "doesn't stretch to the end of the fragmentainer" category (because they
don't do that now). It also puts all other elements (table cells, flex items,
grid items, etc.) into the second category, where the box decorations stretch
into the blank space on at the bottom of the page. I think this is the best
option because with these layout models you'll often have items side-by-side.
I'm guessing it's more likely that the author cares about these items ending
together than that the internal size of the element is consistent with its
specified size. But since we didn't resolve on that, it's open for discussion.

Received on Tuesday, 7 August 2012 23:56:17 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:20 UTC