- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Sun, 19 Jul 2020 23:06:10 +0000
- To: public-css-archive@w3.org
fantasai has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-inline-3] leading-trim vs fragmentation == From https://github.com/w3c/csswg-drafts/issues/3240#issuecomment-433628531 > Fragmentation is an interesting case. It's quite reasonable to want the text-trim to take effect at fragmentation breaks in multicol. But for pages, we'd end up trimming any ink that leaks over. We'll either need to adjust css-page-3 to not trim [ink] overflow at fragmentation boundaries or add a page-padding property similar to scroll-padding or something. This is actually necessary for ruby to work properly in Japanese, and many other effects that require the top of the text to line up across fragmentainers but allows some lines to contain content that overflows that visual line. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5335 using your GitHub account
Received on Sunday, 19 July 2020 23:06:11 UTC