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

Re: Fwd: [css3-multicol] Section 8.1: Overflow inside of multicol elements and positioning

From: Robert O'Callahan <robert@ocallahan.org>
Date: Sat, 17 Aug 2013 10:00:10 +1200
Message-ID: <CAOp6jLYfJT9BFpU9RRnrMrim6P-pTcpYJ9RL3nPMu_pgBmSg+Q@mail.gmail.com>
To: Morten Stenshorne <mstensho@opera.com>
Cc: "www-style@gtalbot.org" <www-style@gtalbot.org>, Scott Johnson <sjohnson@mozilla.com>, "www-style@w3.org" <www-style@w3.org>
On Sat, Aug 17, 2013 at 8:11 AM, Morten Stenshorne <mstensho@opera.com>wrote:

> >> My first question is: What is the desired behavior in this situation? We
> >> should probably adjust the spec to account for this type of situation.
> I'm not sure. The Presto behavior (don't break unbreakable content; just
> overflow at the bottom of the column) is nice if overflow is actually
> visible, which is the case for regular multicol, but not so nice if
> overflow is hidden and unreachable, e.g. for paged media or
> overflow:paged.
> While it may be ugly to brutally slice unbreakable content, at least
> what WebKit does can be done consistently for all kinds of fragmented
> content, regardless of it being multicol, paged media or regions, since
> it guarantees that everything will be visible and reachable somehow.

The issues around visual slicing were analyzed in this thread:
It sort of petered out, but it would probably be better to extend that
thread rather than repeat it.

Jtehsauts  tshaei dS,o n" Wohfy  Mdaon  yhoaus  eanuttehrotraiitny  eovni
le atrhtohu gthot sf oirng iyvoeu rs ihnesa.r"t sS?o  Whhei csha iids  teoa
stiheer :p atroa lsyazye,d  'mYaonu,r  "sGients  uapr,e  tfaokreg iyvoeunr,
'm aotr  atnod  sgaoy ,h o'mGee.t"  uTph eann dt hwea lmka'n?  gBoutt  uIp
waanndt  wyeonut  thoo mken.o w  *
Received on Friday, 16 August 2013 22:00:37 UTC

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