- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 15 Feb 2023 16:57:17 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-overflow-3] how do overflow: clip/hidden combinations interact with rounded borders?`, and agreed to the following: * `RESOLVED: border radius doesn't round the clipping region when mixing overflow: visible and clip` <details><summary>The full IRC log of that discussion</summary> <emilio> dbaron: I missed oriol's last comment, but I think it's relatively simple<br> <emilio> ... I noticed that the spec allows overflow to be clip in one axis but visible in other axis<br> <emilio> ... which is something that was introduced when clip was introduced<br> <emilio> ... when we introduced clip the question is how it interacts with rounding of borders<br> <emilio> ... I thought the simple question is that you clip in one axis but not on the other border radius has no effect<br> <emilio> ... oriol posted screenshots, and I'm not sure browsers are doing this new clip and visible behavior<br> <emilio> oriol: the behavior in browsers is... webkit has a bug where content is not painted... Chromium if it has overflow: visible clip as just clip only with non-zero radius<br> <emilio> ... so not continuous<br> <emilio> ... firefox applies the rounded clip to the bounding rectangle of the overflowing content<br> <emilio> ... In this particular case it looks kind of nice but it can be strange<br> <emilio> ... I think I'm leaning towards dbaron's proposal<br> <fantasai> +1 to dbaron's proposal<br> <flackr> +1 to dbaron's proposal, it makes sense that allowing visible overflow in the off-axis means there's no rounding<br> <emilio> smfr: I think I agree. The WebKit bug was fixed and now we behave like Chromium but I think that's just bugs, I'm ok with dbaron's proposal<br> <emilio> proposed resolution is that when clip and visible are specified, border radius has no effect<br> <fantasai> (on the content)<br> <fantasai> emilio: what if some corners have no radius and others do?<br> <dbaron> s/has no effect/doesn't cause rounded clipping of the contents/<br> <emilio> dbaron: we're not talking about whether border-radius has an effect, but whether it clips the contents<br> <emilio> ... border-radius with overflow: visible has an effect but doesn't clip<br> <emilio> ... my argument is that if you're not clipping in one axis you shouldn't clip to the border radius<br> <emilio> smfr: so basically everything should render as the first Firefox screenshot right?<br> <emilio> ... is that right if there's no content to clip?<br> <emilio> smfr: I'd like to see a test-case with something that overflows only on one side but doesn't fill the content box<br> <emilio> dbaron: I don't think any engine does what the spec says to me<br> <emilio> dbaron: oh wait, FF does it<br> <emilio> dbaron: I'll paste a modified test-case in the issue<br> <emilio> dbaron: https://github.com/w3c/csswg-drafts/issues/7434#issuecomment-1431669370<br> <emilio> dbaron: I think it should match up with what FF is doing on the later one<br> <emilio> ... because the inset rules for the clipping cause that to not have any rounding<br> <fantasai> emilio: I think I'm fine with dbaron's proposal<br> <fantasai> emilio: could do something more complicated, but unclear it would be useful<br> <TabAtkins> ok lol i finally looked at firefox's behavior with dbaron's increased overflow, that's silly<br> <TabAtkins> i see why that would happen but still<br> <emilio> Proposed resolution: border radius doesn't round the clipping region when mixing overflow: visible and clip<br> <emilio> dbaron: I should probably clarify that this is just a bugfix in the spec because nobody thought about it<br> <emilio> ... but I don't think there's any other sensible behavior here<br> <emilio> smfr: if you look in Firefox at the penultimate box on the last test-case I just posted (where I just shift the box) is that what you're proposing?<br> <emilio> astearns: so with this resolution we'd still round the border but the overflowing element isn't clipped<br> <fantasai> fantasai: afaict, all we're proposing here is that the border/background/etc are still rounded as normal, we just don't clip the content to the radius when there's overflow in one axis<br> <fantasai> (or both axes)<br> <fantasai> fantasai: this seems fine, what's the confusion?<br> <emilio> smfr: I just want to confirm that in my latest test-case FF is correct, except for the rounding on the left side<br> <emilio> dbaron: rithg<br> <emilio> right*<br> <emilio> smfr: sounds good<br> <emilio> +1 as well<br> <emilio> RESOLVED: border radius doesn't round the clipping region when mixing overflow: visible and clip<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7434#issuecomment-1431683702 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 15 February 2023 16:57:19 UTC