- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Wed, 06 May 2020 03:59:49 +0000
- To: public-css-archive@w3.org
My mental model is the following [excepting `top` and `bottom` values of `vertical-align`]: 1. Within a ruby base container, ruby bases are aligned exactly as they would be if they were inline boxes on the same line. The ruby base container is drawn around these aligned boxes. (Note that even if we treat them as `vertical-align: baseline` always, they still need to be aligned together, since their font sizes may differ. So there's no reason not to take into account other `vertical-align` values as well.) 2. Within a ruby annotation container, ruby annotations are aligned exactly as they would be if they were inline boxes on the same line. The ruby annotation container is drawn around these aligned boxes. 3. Ruby annotation containers are stacked above/below ruby base containers. Wrt `top` and `bottom` (and the proposed `center` value), I'm happy to treat these all as `baseline`. Alternately, if we want, we can handle these by aligning with respect to the base/annotation container (rather than wrt the line), e.g. for base containers we make sure they're at least as tall as the tallest top/bottom/center-aligned base, and then at the end shift that base up/down to align it as requested within the base container. I don't think honoring `vertical-align` is particularly critical either way, so I don't mind if it is completely ignored for Level 1 implementations. But if we honor it, I think it should affect layout in the way I describe, to be consistent with inline layout generally. Regardless, I do think it's important that ruby bases and annotations are responsive to changes in `dominant-baseline`. -- GitHub Notification of comment by fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4987#issuecomment-624429451 using your GitHub account
Received on Wednesday, 6 May 2020 03:59:51 UTC