W3C home > Mailing lists > Public > www-style@w3.org > April 2016

Re: [css3-break] fragment selectors

From: Joshua Baker <jtbaker@jtbaker.name>
Date: Tue, 19 Apr 2016 10:25:02 -0400
Message-ID: <CAMrnN-hHBux+KCAVYjaYmiPQ5d8OKdDbsAswZwYpv0AC0iY=xQ@mail.gmail.com>
To: Matt Haggard <haggardii@gmail.com>
Cc: www-style@w3.org
Can I suggest we call the pseudo-classes `:widow` and `:orphan`, to reflect the
existing Fragmentation Module draft
<https://drafts.csswg.org/css-break/#widows-orphans>?

`:breaks-on-to-next-page` becomes `:orphan`, matching the parts of element
which has additional parts on a later page.
`:breaks-from-prev-page` becomes `:widow`, matching the parts of element
which has additional parts on an earlier page.

On Thu, Apr 14, 2016 at 12:55 PM, Matt Haggard <haggardii@gmail.com> wrote:

> The box-decoration-break property lets me have an element broken across
> pages where the first half of the element lacks a bottom border and the
> last half of the element (on page 2) lacks a top border.  This is a good
> step, but I'd really like to have control over the styling of the fragments
> separately.  Something like:
>
> div:breaks-on-to-next-page {
>   ...
> }
> div:breaks-from-prev-page {
>   ...
> }
>
> (My naming is terrible, yes).  This would let me make the breakage more
> obvious as shown in this image:
>
> [image: Inline image 1]
>
> Thanks!
>
> (Did I send this to the right place?)
>
> Matt Haggard
>

scissors.png
(image/png attachment: scissors.png)

Received on Tuesday, 19 April 2016 14:26:27 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:09:02 UTC