- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Fri, 05 Feb 2021 06:32:05 +0000
- To: public-css-archive@w3.org
> I suppose this would have no effect under ruby-merge:auto, which already let internal overhang happen anyway. I think if we define internal overhang over annotationless bases to behave similarly to external overhang over adjacent text, it should behave the same under `separate` and `auto`. `auto` should only be only different in that it allows sharing space across adjacent bases. > That said, while I think we could specify something like this, I am unconvinced it is worth it. We already have plenty of moving parts and a decently complicated model, and I'd rather we first got the basics down. If internal overhang is less common than external overhang, then we can defer it to L2. But if the general expectation is that internal overhang behaves like external overhang, then we should spec it as such now. -- GitHub Notification of comment by fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1908#issuecomment-773824843 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 5 February 2021 06:32:07 UTC