- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 20 Mar 2024 15:59:10 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-box-4] border-radius and border-image should be "border properties"`, and agreed to the following: * `RESOLVED: no change to spec` <details><summary>The full IRC log of that discussion</summary> <chrishtr> TabAtkins: we have a list of properties allowed in position-try. As fantasai said, we want to keep that list as short as possible<br> <chrishtr> TabAtkins: one of the currently allowed properties is border. This is in order to do things like thickening borders when adjacent to the anchor.<br> <chrishtr> TabAtkins: right now this is specified as "the border properties". Which in the other specs says "border width, style" but not border-radius and border-image.<br> <chrishtr> TabAtkins: should we include border-radius and border-image?<br> <chrishtr> TabAtkins: makes sense to me to include border-radius.<br> <chrishtr> TabAtkins: no opinion about border-image, but can just skip it<br> <iank_> q+<br> <Rossen_> ack fantasai<br> <chrishtr> fantasai: my inclination would be to exclude both on the principle that we'd need to solve conditional styling on sides for these to be useful.<br> <chrishtr> fantasai: OTOH inset, margin, width and height are more about positioning on the screen than styling visually<br> <chrishtr> iank_: agree. Allowing these additional properties would be invasive and more complex.<br> <kizu> +1<br> <chrishtr> fantasai: better to focus on positioning only when possible<br> <chrishtr> fantasai: can see how people would want to include border though, because it affects the box<br> <kizu> q+<br> <chrishtr> Rossen_: border box sizing is still prevalent in terms of use<br> <miriam> box-sizing only helps if you set an extrinsic size - it doesn't help with intrinsic size boxes + padding/borders<br> <chrishtr> Rossen_; wouldn't be happy as a user to anchor to a corner of a box and based on the box sizing property it may or may not include padding / border<br> <chrishtr> Rossen_: not totally sure if it makes a difference?<br> <chrishtr> TabAtkins: regardless of box sizing, you're not changing the border at all, but just the content box?<br> <chrishtr> iank_: don't think the box sizing property doesn't matter too much. Some layout modes may change the internals though. e.g. tables differs.<br> <Rossen_> ack kizu<br> <Zakim> kizu, you wanted to expand on that +1 ? :) and to<br> <chrishtr> kizu: my +1 is for what fantasai said for not including border at all in try blocks<br> <chrishtr> kizu: for most use cases it should be possible to move the element via other positioning to make room for borders, without allowing borders in position-try<br> <iank_> https://github.com/w3c/csswg-drafts/issues/9195#issuecomment-1942297101<br> <chrishtr> kizu: everything else in position-try positions only but border may affect colors which is not a great fit for position-try<br> <chrishtr> chrishtr: TabAtkins can we just exclude border?<br> <chrishtr> TabAtkins: yes, and in fact I got confused and border is already not in the spec. Ok to resolve no change to spec.<br> <TabAtkins> https://drafts.csswg.org/css-anchor-position/#accepted-position-try-properties<br> <chrishtr> RESOLVED: no change to spec<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9245#issuecomment-2009923791 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 20 March 2024 15:59:11 UTC