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 15:46:03 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-553461379-1573659962-sysbot+gh@w3.org>
The given example seems entirely academical to me. Borders that are larger than the entire size of the fragmentainer isn't something that occurs in practice. So I don't see a need to spec this particular edge case. The spec is already clear that slicing borders are strongly discouraged.

If anything, I'd like to see the "you MAY slice monolithic content" escape hatch **removed** so that CSS fragmentation behaves more like it does in physical printed media. You would **never** see a sliced border there!

The path to better interop here is to agree to stop slicing altogether and instead implement what css-break actually recommends, because it's pretty good. This is the path Gecko will take. (And the problem in Chrome isn't just borders, it's also [grid rows](https://bugs.chromium.org/p/chromium/issues/detail?id=613341) and a whole range of other situations, as @mrego alludes to with "The whole engine has issues with fragmentation". I'm hoping LayoutNG will bring some improvements to Chrome's fragmentation...)

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

This archive was generated by hypermail 2.4.0 : Saturday, 2 July 2022 03:21:25 UTC