- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 22 May 2024 17:00:53 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-anchor-position] Alignment shouldn't interfere with sizing`.
<details><summary>The full IRC log of that discussion</summary>
<emilio> fantasai: the current anchor-center definition changes the avail size for sizing the abspos to the largest rect that can be centered wrt the anchor that fits within its inset area<br>
<emilio> ... so if your anchor is in the center on the screen you have all the regular stuff<br>
<TabAtkins> q+<br>
<emilio> ... but if you're in the edge of the screen you have a little bit of space<br>
<emilio> ... alignment never affects the avail space<br>
<emilio> ... this would be a first<br>
<iank_> q+<br>
<emilio> ... alignment takes the box and avail space and alings it<br>
<emilio> ... I think that's what we should do for anchor-center<br>
<emilio> ... if the author wants to resize the anchor we should provide keywords in the inset or what not properties to enable that<br>
<astearns> ack TabAtkins<br>
<emilio> ... so I think the anchor-center kw should say "size the box in this container, and move it as close to the desired alignment without overflowing the container"<br>
<emilio> TabAtkins: this is novel for alignment<br>
<emilio> ... but that's not needed for existing alignment values<br>
<emilio> ... this isn't true for anchor-center<br>
<emilio> ... if half your size is larger than the distance to the closer edge<br>
<emilio> ... then you overflow if you stay centered<br>
<emilio> ... in particular if you fill the cb then you're almost guaranteed to overflow<br>
<emilio> fantasai: that's not what I'm proposing tho<br>
<emilio> TabAtkins: right, two posibilities<br>
<emilio> ... (1) is the current behavior<br>
<emilio> ... which has this edge case but looks good pretty good if you're in the middle<br>
<emilio> ... looks better than growing to the full size and align<br>
<emilio> ... (2) is what you suggest<br>
<emilio> ... this was what the spec originally said<br>
<emilio> ... but the sliding behavior needs to be available to more than anchor-center<br>
<emilio> ... bikeshed does this for left-aligned anchors for example<br>
<emilio> ... but whatever you do it can't be locked to anchor-center<br>
<emilio> ... when we come up with something that does the sliding, it should disable this shrink-avail-size bit<br>
<fantasai> una made a visual of this issue in https://github.com/w3c/csswg-drafts/issues/9960#issuecomment-1944518084<br>
<emilio> ... so I wrote the spec the way it is because it looks better in the majority of cases<br>
<emilio> ... you can kinda fix this with min-size (though it's not perfect because you'd overflow)<br>
<emilio> ... but when we have the sliding bit then it should work just fine<br>
<astearns> ack iank_<br>
<emilio> ... if we do the sliding I'm concerned about doing it too early before knowing what it'd look more generally<br>
<emilio> iank_: we do have changing of avail space in inset-{axis}: auto in rtl<br>
<emilio> ... there are cases where this happens<br>
<astearns> ack fantasai<br>
<emilio> fantasai: yeah static pos...<br>
<emilio> ... I see what your concern is<br>
<emilio> ... there's another issue I filed that should get us there<br>
<emilio> ... I feel strongly that alignment should not change sizing<br>
<emilio> ... my suggestion is that maybe we defer this issue, we have a chat about the other issue<br>
<emilio> ... if we have a system that works then we can come back to this issue<br>
<emilio> ... I'd much rather give authors control about this<br>
<emilio> TabAtkins: what's the other issue?<br>
<emilio> fantasai: #10316<br>
<kizu> +1 to fantasai that align should not resize things, I had cases in my experiments where this behavior was not what I wanted, and I almost would always prefer sliding behavior (which _sounds_ like something close to how `position: sticky` could work)<br>
<emilio> TabAtkins: happy with that<br>
<emilio> ... there are slight tricks we could do to minimize the<br>
<emilio> ... bad case here<br>
<emilio> ... but we can chat<br>
<emilio> astearns: let's leave open and come back after TabAtkins and fantasai have discussed the other one<br>
<TabAtkins> ah yeah i haven't seen 10316 yet, cool<br>
</details>
--
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10315#issuecomment-2125321730 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 22 May 2024 17:00:54 UTC