- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 24 Jan 2024 18:01:21 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-inline-3] text-box-trim vs fragmentation `, and agreed to the following: * `RESOLUTION: ink-overflow spills out of the page content area into padding and margins, user agents that can't draw paint overflow may shift content down to avoid clipping` * `RESOLVED: Should text-box-trim apply at fragmentation breaks, depend on the box-decoration-break property` <details><summary>The full IRC log of that discussion</summary> <Frances> github-bot #335<br> <Frances> fantasai: One consideration is when requesting text-box:trim, if it lands at the top of the page, we have ink spilling out of the page. Currently gets clipped out. If specifying cap height and land at the top of the page, accent marks will get clipped.<br> <Frances> fantasai: Do we want to specify that ink-overflow can spill onto the padding area and if so do we want to allow implementations to pull content. How to approach the problem of clipping?<br> <Frances> fantasai: Trim at the bottom of the page or at the next page? We need some way to control it and make it happen, with a consistent top edge.<br> <bradk> +1 to allowing ink to spill over, similar to box-shadow<br> <Rossen_> q?<br> <Frances> fantasai: Need a way to handle text-box-trim for the correct padding and border of content. Two issues: clipping and separate control for fragmentation breaks.<br> <fantasai> s/Need a way to handle text-box-trim for the correct padding and border of content./If using text-box-trim for correct spacing between content and border, don't necessarily want to trim at fragmentation breaks/<br> <Frances> chris h: Bbecause it is more difficult to implement with more complexities, text-box-trim does not apply for printing<br> <Frances> Rossen: Allows for additive behavior in the future. Need to specify it correctly.<br> <fantasai> s/Trim at the bottom/Other question is, if the paragraphs fragments in the middle, do we trim at the bottom/<br> <astearns> -1 to not applying to print. Would there be a way to allow it in print except for at page breaks?<br> <Frances> Florian: Need to define cleanly the boundary. In typography such as using css to make printed material or like printing. About fragmentation, should not say print, possibly relevant.<br> <Frances> Florian: Needs to work for printing. We need to work on this and not call the compat trap.<br> <Frances> fantasai: Shouldn't disable trim for printing, need to spec the ideal behavior to the extent that it can be printed. Might allow user agents that can't do that, shift it down the page to use the text glyphs.<br> <Rossen_> ack fantasai<br> <Frances> chris h: The two together sound fine.<br> <Frances> PROPOSAL: ink-overflow spills out of the page content area into padding and margins, user agents that can't draw paint overflow may shift content down to avoid clipping.<br> <fantasai> s/paint overflow/ink overflow/<br> <fantasai> +1<br> <Frances> rossen: objections?<br> <Frances> RESOLUTION: ink-overflow spills out of the page content area into padding and margins, user agents that can't draw paint overflow may shift content down to avoid clipping<br> <Frances> fantasai: A question around text-box-trim taking affect. Should be a separate property to control them indepdently.<br> <Frances> Chris H: Specify in the property, not overflow between columns.<br> <Rossen_> s/RESOLUTION/RESOLVED/<br> <dbaron> s/Specify in the property/just operates at the top of the first fragment and the bottom of the last fragment/<br> <dbaron> fantasai: I'd want it to follow box-decoration-break<br> <Frances> PROPOSAL: Should text-box-trim apply at fragmentation breaks, depends on the box-decoration-break property<br> <Frances> Rossen: Objections?<br> <Frances> RESOLVED: Should text-box-trim apply at fragmentation breaks, depend on the box-decoration-break property<br> <chrishtr> Thanks all!<br> <Frances> fantasai: fragmentation case possibly need an independent control. Could be a separate feature.<br> <Rossen_> Zakim, end meeting<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5335#issuecomment-1908655635 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 24 January 2024 18:01:23 UTC