W3C home > Mailing lists > Public > www-style@w3.org > February 2015

Re: [css-break][css-overflow-3][css-regions][css4-ui] generalizing 'region-fragment' into a fragmentation primitive: a first step to solving multi-line ellipsis

From: fantasai <fantasai.lists@inkedblade.net>
Date: Mon, 09 Feb 2015 03:49:36 -0500
Message-ID: <54D874A0.3080003@inkedblade.net>
To: www-style@w3.org
On 01/20/2015 08:13 AM, Florian Rivoal wrote:
> [... lots of stuff ...]

Florian and I were bikeshedding the fragmentation property after-hours.
(Briefly, this is a new property that is split off from 'overflow',
taking along all the fragmentation-related values.)

Proposal so far is

   continue: auto | overflow | paginate | clone | discard | next

   overflow - content that doesn't fit overflows, according to 'overflow'

   paginate - content that doesn't fit paginates (formerly overflow: paged)
              This creates a paginated view inside the element similar to
              the way that 'overflow: scroll' creates a scrollable view.
              Pages can be styled with @page rules. Print is effectively
              continue: paginate on the root.

   clone - content that doesn't fit causes the element to copy itself
           and continue laying out (formerly overflow: fragment)

   discard - content that doesn't fit is discarded at a fragmentation
             break (generalized from region-fragment: break; on the
             last region of a region chain)

   next - content that doesn't fit is pushed to the next region. If
          there isn't a next region, it overflows. [Behavior could
          have been to discard, but I think discarding anything should
          be a very explicit behavior.]

Received on Tuesday, 10 February 2015 03:08:57 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:52:01 UTC