[csswg-drafts] [css-break] Empty fragment at fragmentainer boundary

• From: Morten Stenshorne via GitHub <sysbot+gh@w3.org>
• Date: Wed, 14 Jun 2017 15:27:06 +0000
• To: public-css-archive@w3.org
• Message-ID: <issues.opened-235918988-1497454024-sysbot+gh@w3.org>

mstensho has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-break] Empty fragment at fragmentainer boundary ==
https://drafts.csswg.org/css-break/

If we have an empty, zero-height block, and it occurs exactly at a fragmentainer boundary, where should it end up? In the former fragmentainer, or in the latter?

<div style="columns:2: column-fill:auto; height:100px;">
    <div style="height:100px;"></div>
    <div id="empty"></div>
    <div style="height:50px;"></div>
</div>

Is #empty in the first or second column? If the answer is "second", then how about:

<div style="columns:2: column-fill:auto; height:100px;">
    <div style="height:100px;"></div>
    <div id="empty"></div>
</div>

Should we establish a second column just to hold an empty fragment?

This may not matter for painting and hit-testing, but it's exposable via e.g. getClientRect().

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1529 using your GitHub account

Received on Wednesday, 14 June 2017 15:27:12 UTC