- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Thu, 07 Jan 2021 00:55:33 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-overflow-3] Add box-edge values to overflow-clip-margin`, and agreed to the following: * `RESOLVED: Add the box keywords to the overflow-clip-margin` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: [css-overflow-3] Add box-edge values to overflow-clip-margin<br> <tantek> no objection, though it does feel odd to use terms as "English meaning" that are used more precisely by other specs<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/5801<br> <dael> fantasai: A lot of confusion in chrome bug by authors that expected border edge to a box [missed]. It has borders and radius and it clips to the inner edge. In corner with curve it clips to curved edge. Looks a bit weird if contents are only replaced element. Why doesn't it clip to content edge?<br> <dael> fantasai: If you spec padding and borders on replaced element b/c it curves the edges of the box including content the replaced lement will get a curved edge. But if you do it on a container the contents still show.<br> <dael> fantasai: Frequently wante.d WE have overflow clip margin that takes a length and let syou clip a little outside the box. Could add content-box padding-box and border-box as keywords that sets hte margin to the appropriate offset.<br> <dael> fantasai: That's the use case and proposal. Question is do we want to do that?<br> <dael> astearns: Keywords alone or supply an length?<br> <dael> fantasai: Keywords alone, length, or combo<br> <dael> florian: Reasonable. What is impl interest?<br> <dael> chrishtr: I think it's okay. Tried impl a couple months ago and it was easy<br> <dael> smfr: I need more pictures, hard to understand. insetting the inner curved border radius by some amount?<br> <dael> chrishtr: top of issue greena nd red, they want inner and outer curve to match<br> <dael> smfr: White stripe is padding and they want that curved?<br> <dael> chrishtr: Yep<br> <dael> myles: It's possible to achieve that. This prop is to make it earlier?<br> <dael> fantasai: Yeah, you'd need a wrapper element to get that otherwise. And you'd have to match the radius correctly. You can do it but it's awk<br> <dael> smfr: Always insert not outset?<br> <dael> fantasai: A postive value outsets from the edge it would clip. So you can outset or inset. Prop here is add keywords that match the box edge<br> <dael> smfr: And if you outside child elements paint on top of border?<br> <dael> fantasai: Year<br> <dael> smfr: And this is ones without overflow hidden?<br> <dael> fantasai: You'd need to apply a clip<br> <dael> smfr: Also about clippath?<br> <dael> florian: Not clip path. Overflow<br> <dael> smfr: Inset the rectangle and recompute border radius that's okay.<br> <dael> fantasai: Just about inset and outset from border edge for overflow prop<br> <dael> smfr: Okay<br> <myles> s/earlier/easier/<br> <fantasai> https://drafts.csswg.org/css-overflow-3/#overflow-clip-margin<br> <dael> dholbert: It sounds like this is clipping padding sep than clipping content?<br> <dael> fantasai: Currently have overflop clip margin. If we allow a content-box value we would need to inset. It would clip contents, not the element.<br> <dael> chrishtr: It already only clips content. This changes dimensions of clip. Size and border radius<br> <florian> q+ to ask about interaction with corner-shape<br> <dael> dholbert: Padding is clipped at curved border and that controls wehre content is clipped<br> <dael> chrishtr: Padding is clipped as normal.<br> <dael> fantasai: By the background-clip<br> <dael> chrishtr: What you can already spec as different rectangles. This is only apply to content<br> <dael> Rossen: Is there any additional implications to box shadow?<br> <dael> fantasai: Doesn't effect. Only effects content<br> <astearns> ack florian<br> <Zakim> florian, you wanted to ask about interaction with corner-shape<br> <dael> florian: We just talked through how it only effects normal border box. In BG4 we had corner shape prop to cut at an angle. Expectation is will have new corner shapes that might make impl a bit harder.<br> <dael> florian: Doesn't change usefulness, but does it change concern on impl?<br> <dael> chrishtr: Does this thing let you spec the angle?<br> <dael> florian: Only switch from rounded to a straight diaganal line right now. May expand to different corner shapes.<br> <dael> myles: Not sure there would be consensus this property you desc would grow. Used to have more values and we got rid of them. I'd be surprised if we add a lot more<br> <dael> chrishtr: I would agree. It already has the need to geometrically expand or contract without complex code. I don't think we would spec difficult cases<br> <dael> florian: Cool. I was just hoping that we weren't missing a case for complexity<br> <dael> fantasai: Drawing the complex border is a bigger problem then changing the clip<br> <dael> astearns: I think I heard q from each implementor<br> <dael> astearns: Sounds like consensus to add these keywords to overflow-clip-margin<br> <dael> astearns: Concerns?<br> <dael> astearns: Add the box keywords to the overflow-clip-margin<br> <dael> astearns: Obj?<br> <dael> dholbert: border-box, padding-box, content-box?<br> <dael> fantasai: Yes<br> <dael> fantasai: padding-box is default<br> <dael> chrishtr: Can the syntax be impl incrementally? Someone impl lengths and add this later?<br> <dael> fantasai: Should be fine. As long as you don't parse the syntax you don't impl it's good<br> <dael> RESOLVED: Add the box keywords to the overflow-clip-margin<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5801#issuecomment-755815008 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 7 January 2021 00:55:39 UTC