Re: [csswg-drafts] [css-anchor-position-1] Define scroll interaction better. (#10858)

The CSS Working Group just discussed `[css-anchor-position-1] Define scroll interaction better.`.

<details><summary>The full IRC log of that discussion</summary>
&lt;kbabbitt> emilio: the timing of the operation was already discussed<br>
&lt;kbabbitt> ..seems we should put it somewhere in HTML, not talk about it here<br>
&lt;kbabbitt> ...other problem is that the whole anchor element doesn't resolve<br>
&lt;kbabbitt> ...depends on whether there's an anchor function which means that gCS doesn't round trip anymore<br>
&lt;kbabbitt> ...feels quite unfortunate<br>
&lt;kbabbitt> ...setting the inset to a fixed value would remove the anchor ness and that would just break positioning<br>
&lt;kbabbitt> ... that seems kind of bad<br>
&lt;kbabbitt> TabAtkins: that is the case, I agree it's bad, we have a case or two of that already with the shadow related things we were talking about before<br>
&lt;kbabbitt> ...agree they're not great<br>
&lt;kbabbitt> ...don't know how to get around it unless we add a syntax to let it reflect the fact that there was an anchor<br>
&lt;kbabbitt> ...indicate that it was anchored even though you're using an explicit value<br>
&lt;kbabbitt> emilio: could also include scroll offset in resolved value but that might be weird too<br>
&lt;kbabbitt> TabAtkins: I'd have to think about that, might work<br>
&lt;kbabbitt> emilio: we can think about it and figure out a solution<br>
&lt;kbabbitt> TabAtkins: would not mind coming up with something that addresses this problem, let's see what we can do in the issue<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10858#issuecomment-2379889668 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 27 September 2024 19:03:56 UTC