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

Re: [csswg-drafts] [css-break] Tall unbreakable content - overflow or slice? (#4509)

From: Mats Palmgren via GitHub <sysbot+gh@w3.org>
Date: Wed, 13 Nov 2019 22:14:24 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-553629176-1573683263-sysbot+gh@w3.org>
I believe treating tall images as monolithic by default is the best option, as the spec suggests. The current behavior in Gecko is [a bug](https://bugzilla.mozilla.org/show_bug.cgi?id=1372836) in my opinion (and Chrome appears to do better there). Again, you would never see a photograph being sliced between columns or pages in a printed magazine. I don't see why CSS layout should do that by default.  Granted, a browser needs to handle all possible content, so we need to handle the edge case where an image is taller than its fragmentainer for example. Slicing is one option, but we could also try scaling it down until it fits for example. Fwiw, in the bug above, I suggested adding `img, video, ... { break-inside:avoid; }`in our UA sheet to improve our layout, which would also give authors a way to override that default behavior if they wish. Giving authors more control over the mechanism (slice/scale/overflow/truncate/ellipsing/etc) seems like a good idea too.

GitHub Notification of comment by MatsPalmgren
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4509#issuecomment-553629176 using your GitHub account
Received on Wednesday, 13 November 2019 22:14:26 UTC

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