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

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

From: fantasai via GitHub <sysbot+gh@w3.org>
Date: Wed, 14 Nov 2018 21:18:33 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-380890886-1542230312-sysbot+gh@w3.org>
fantasai has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-break-3] Should 'break-before' / 'break-after' have an 'always' value? ==
We decided not to have an 'always' value for break-* because it wasn't clear to us whether this should create a break within the nearest fragmentation context, or all the way up to the top level. (Imagine a multicol inside paged media: does 'always' create a column break or a page break?)

However, it looks like IE implements an 'always' value, which has fairly high usage: https://developer.microsoft.com/en-us/microsoft-edge/platform/usage/css/break-before/
We should maybe figure out what it does and spec that.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3318 using your GitHub account
Received on Wednesday, 14 November 2018 21:18:35 UTC

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