W3C home > Mailing lists > Public > public-css-archive@w3.org > November 2018

Re: [csswg-drafts] [css-break-3] Should 'break-before' / 'break-after' have an 'always' value?

From: fantasai via GitHub <sysbot+gh@w3.org>
Date: Thu, 15 Nov 2018 22:00:48 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-439205951-1542319247-sysbot+gh@w3.org>
OK, I ran some tests. 'break-before: always' in Edge triggers a page break, but only when printing. I don't think this makes particularly much sense, though.

We have the following options:

- A) We define 'break-before: always' to trigger a break at the innermost fragmentation context
- B) We define 'break-before: always' to trigger a break through all available fragmentation contexts.
- C) Edge removes 'break-before: always' from its implementation.
- D) We define 'break-before: always' to be an alias of 'break-before: page'.

My preference would be A if possible, since I suspect it's going to be the most useful behavior. On pages without multicol, the behavior would be the same as Edge has currently. B) Would be more compatible with what Edge is doing right now on pages with multicol. It would additionally trigger breaks in multicol on screen, but pages depending on that are broken already since those breaks already trigger in print. C) seems acceptable, but the usage numbers seem a little high on Edge so it could be problematic. D) is my least favorite option.

-- 
GitHub Notification of comment by fantasai
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3318#issuecomment-439205951 using your GitHub account
Received on Thursday, 15 November 2018 22:00:49 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:39 UTC