- From: Mats Palmgren via GitHub <sysbot+gh@w3.org>
- Date: Mon, 19 Apr 2021 18:04:00 +0000
- To: public-css-archive@w3.org
I agree, `overflow-inline : clip` should not affect the baseline, so that disqualifies the "behave as `hidden`" option as described above. However, I don't see a reason why we can't synthesize a baseline for `overflow-block : clip` (which would behave roughly as `hidden` in that axis). It's also worth considering what happens when the baseline is well within the size, e.g. emilio's test [with `height:100px` instead](http://software.hixie.ch/utilities/js/live-dom-viewer/?saved=9191). I'd slightly prefer the `visible` behavior over a synthesized baseline in this case, but I don't feel strongly about it. There's also a third option: "clamp the baseline", which would calculate the baseline normally (as for `visible`) but clamp it to the clip area. That would make emilio's test behave (roughly*) as `hidden` but the `height:100px` case would still behave as `visible`. (I dunno how complicated that would be to implement though, so I'm not sure if it's worth it.) (*) the clip area is typically the padding box, whereas the `hidden` baseline is calculated from the border box So I see three viable options: 1. the baseline is calculated the same as for `visible` (what Firefox currently implements) 2. always synthesize a baseline for `overflow-block : clip` 3. as 1 but clamp it to the clip area -- GitHub Notification of comment by MatsPalmgren Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6212#issuecomment-822666303 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 19 April 2021 18:04:02 UTC