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

Re: [csswg-drafts] [css-break-4] Should fragmentation of block-level replaced-elements be configurable? ("object-slice") (#3404)

From: Bernhard Fey via GitHub <sysbot+gh@w3.org>
Date: Fri, 07 Dec 2018 10:35:05 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-445191653-1544178903-sysbot+gh@w3.org>
(created #3405 for `orphans` and `widows`)

I have 2 concern with `break-inside`, I'm not sure either is serious enough. For both I assume the `auto` and `avoid` values of `break-inside` and `object-slice` act the same.

1. There is no `none` value. So there would be no way to specify that the image should not be fragmented at all.
a) While this most often will not be the preferred behavior it might be useful, e.g. to optimize layouts that will be further manipulated by JavaScript.
b) Also some authors may (for more or less rational reasons) prefer monolithic elements to not be fragmented.

2. The initial value (`auto`) is not matching the preferred/expected default behavior (`avoid`).
a) User agent style sheets can correct this for the affected HTML elements. However, having to adjust the default behavior of a group of elements, when the engine knows that they all belong to that groups, feels to me like introducing an avoidable redundancy. 
b) Also this would make writing new style sheets for XML with no existing user agent styles more complex. Although I'm not sure whether that is a priority.

GitHub Notification of comment by bernhardf-ro
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3404#issuecomment-445191653 using your GitHub account
Received on Friday, 7 December 2018 10:35:06 UTC

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