- From: Morten Stenshorne <mstensho@opera.com>
- Date: Tue, 20 Dec 2011 14:20:59 +0100
- To: Håkon Wium Lie <howcome@opera.com>
- Cc: fantasai <fantasai.lists@inkedblade.net>, "Robert O'Callahan" <robert@ocallahan.org>, www-style@w3.org
Håkon Wium Lie <howcome@opera.com> writes: > Also sprach Morten Stenshorne: > > > > > "When the multi-column element is paginated, only the last row > > > > of column boxes is affected by 'column-fill'." > > > > I like your proposed text, and I think we should use it. > > > > This doesn't really make sense to me - neither the proposed text here, > > nor what the spec currently says. > > > > <div style="columns:3; column-rule:1px solid; column-fill:auto; orphans:0; widows:0;"> > > <div style="break-after:page;">line<br>line<br>line</div> > > <div style="break-after:page;">line<br>line<br>line</div> > > <div style="break-after:page;">line<br>line<br>line</div> > > </div> > > > > Should we really forcefully balance the columns on the two first pages > > here? > > So, you are saying the the spec shoul not use terms like "not being > affected", but rather about what the behavior should be? That makes sense. > > How about: > > "When the multi-column element is paginated, this last row of > columns are formatted according to the computed value of this > property; other columns are formatted as if 'column-fill: > auto' had been set." I'm just wondering why it only has to apply to the last row. Force-balancing columns in a row before a spanner is something we obviously want, but before a page break? -- ---- Morten Stenshorne, developer, Opera Software ASA ---- ------------------ http://www.opera.com/ -----------------
Received on Tuesday, 20 December 2011 13:21:43 UTC