- From: Koji Ishii via GitHub <sysbot+gh@w3.org>
- Date: Tue, 21 May 2024 16:54:54 +0000
- To: public-css-archive@w3.org
Thank you @jantimon for the great feedback. Let me explain my understanding of the resolution. The #8829 resolved to split the line-box-affecting aspects of `text-box-edge` to a new property (name TBD, tentatively called `text-line-edge`). So, this issue is about multiple _block_ ancestors having different `text-box-edge` properties, as in the examples of the first two comments of this issue. Here's another more artificial example to explain the resolution: ```html <div style="text-box-trim: both; text-box-edge: text"> <div style="text-box-edge: leading"> <div style="text-box-edge: cap text">FIRST</div> <div>MIDDLE</div> <div style="text-box-edge: text alphabetic">LAST</div> </div> </div> ``` Since the resolution is "innermost", the top of the "FIRST" should be trimmed at the `cap` edge, and the bottom of the "LAST" should be trimmed at the `alphabetic` edge. The split in #8829 made applying `text-box-trim` and `text-box-edge` to `<span>` in your examples to have no effects, so your examples will not be impacted by the resolution of this issue. When we start discussing `text-line-edge`, I think your feedback is one of the most important points to discuss about. @fantasai Please correct me if any. -- GitHub Notification of comment by kojiishi Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5426#issuecomment-2123051241 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 21 May 2024 16:54:55 UTC