- From: Robert O'Callahan <robert@ocallahan.org>
- Date: Wed, 6 Mar 2013 12:23:48 +1300
- To: David Hyatt <hyatt@apple.com>
- Cc: Alan Stearns <stearns@adobe.com>, James Holderness <j4_james@hotmail.com>, "www-style@w3.org" <www-style@w3.org>
- Message-ID: <CAOp6jLbf+vzEX8V0Yf+f7XuQHDkkSUWe1o3WSmYoaYk0mUAYmA@mail.gmail.com>
On Wed, Mar 6, 2013 at 9:12 AM, David Hyatt <hyatt@apple.com> wrote: > Note that if the multicolumn block has overflow:hidden (which again will > be common when you're paginating an entire document, you'll see a > bad-looking slice with your approach as well), or you won't see the content > at all if it is fully out of view. > True, but if the relative positioning isn't too large, authors can work around that by adding padding to the multicolumn element. (3) Vertical offsets are in the flow, relative positioned object paginates > at its final position. > (a) Pros - Content is never lost, even when the column block is > clipped. No bad slices ever occur. > (b) Cons - Relative positioning is being taken into account prior to > layout, which does not match the current spec. > Also, this is likely to be insanely hard to implement IMHO. So your use-cases revolve around situations where an author wants to render content they don't control with vertical breaks, there's a real risk it contains transforms or rel-pos that would extend outside any reasonable margins/padding, and scrolling to view such transformed/rel-pos content is not acceptable for some reason, so they're willing to visually slice and accept poor vertical breaks in other situations. If we're going to support those cases I think we should put this under author control instead of forcing authors to accept a tradeoff that doesn't make sense for them. Also, I think we should study your cases in more detail. For one thing, if authors want to handle HTML they don't control, they may well want to load it in a (possibly sandboxed) iframe, so we'd really need a way to do visual-slicing pagination of <iframe> content, which IE10 regions supports but CSS multicol doesn't. Rob -- Wrfhf pnyyrq gurz gbtrgure naq fnvq, “Lbh xabj gung gur ehyref bs gur Tragvyrf ybeq vg bire gurz, naq gurve uvtu bssvpvnyf rkrepvfr nhgubevgl bire gurz. Abg fb jvgu lbh. Vafgrnq, jubrire jnagf gb orpbzr terng nzbat lbh zhfg or lbhe freinag, naq jubrire jnagf gb or svefg zhfg or lbhe fynir — whfg nf gur Fba bs Zna qvq abg pbzr gb or freirq, ohg gb freir, naq gb tvir uvf yvsr nf n enafbz sbe znal.” [Znggurj 20:25-28]
Received on Tuesday, 5 March 2013 23:24:16 UTC