- From: Håkon Wium Lie <howcome@opera.com>
- Date: Tue, 8 Oct 2013 11:24:43 +0200
- To: Morten Stenshorne <mstensho@opera.com>
- Cc: www-style@gtalbot.org, "W3C www-style mailing list" <www-style@w3.org>
Morten Stenshorne wrote:
> > The example I have in mind is a spanner that naturally appears right
> > before or after a page break. Its bottom (or top) margin will be
> > "collapsed" with the multicol container.
>
> "Collapse" with the page (or "outer fragmentation context", to be more
> precise), not the multicol container, I assume?
Yes.
> > But perhaps "collapsing" isn't the right term, the spec uses
> > "truncated":
> > http://dev.w3.org/csswg/css-break/#break-margins
>
> <div style="columns:3;">
> ....
> <!-- natural page break occurs here -->
> <div style="column-span:all; margin-top:50px;">...</div>
> </div>
>
> You're saying that the 50px top margin should be eaten and forgotten
> about when it adjoins a natural/unforced break? I agree.
Yes, good.
> > Spanners create new block formatting contexts, but their margins can
> > be changed by their surroundings. In this example, two spanners
> > naturally end up at the top of a page. The top margin of the first
> > spanner is truncated due to being after an unforced break.
>
> That doesn't look like an unforced break; that looks like the FIRST
> page. And since there's a blue border preceding the spanner as well,
> it's not even at the beginning of the page. So this looks wrong to me.
Good point. I've revised the example, both visually and code-wise.
Could you have another look?
-h&kon
Håkon Wium Lie CTO °þe®ª
howcome@opera.com http://people.opera.com/howcome
Received on Tuesday, 8 October 2013 09:25:20 UTC