Re: [csswg-drafts] [css-anchor-position] Should scroll-margin/padding have an effect on position-visibility: anchors-visible? (#10410)

The CSS Working Group just discussed `[css-anchor-position] Should scroll-margin/padding have an effect on position-visibility: anchors-visible?`, and agreed to the following:

* `RESOLVED: revert previous resolution`

<details><summary>The full IRC log of that discussion</summary>
&lt;JoshT> TabAtkins: based on a prev resolution, resolved anchors visible takes scroll-padding and scroll-margin into account<br>
&lt;JoshT> ... if ??? in the scroll padding zone, it will count as no longer visible and make the containing element disappear as well<br>
&lt;TabAtkins> s/containing/anchoring/<br>
&lt;TabAtkins> s/???/anchor element/<br>
&lt;JoshT> ... further thoughts: that might not make sense. and doesn't do---<br>
&lt;JoshT> ... the intent was that if you have stickypos or fixedpos header and you have scroll-padding to account<br>
&lt;JoshT> ... it would let you respond to that and ???? if it got obscured<br>
&lt;JoshT> ... you had to guess the size of the obscuring element<br>
&lt;JoshT> ... there is an auto value for scroll padding saying it's capable for doing this but no one does that<br>
&lt;JoshT> ... our conclusion me and fantasai was to revert previous resolution<br>
&lt;JoshT> ... and only care about when the anchor goes out of the scrollable area completely<br>
&lt;JoshT> ... and then later solve the obscuring header problem properly, both for scroll padding and this issue<br>
&lt;JoshT> PROPOSED: revert previous resolution<br>
&lt;emilio> seems fine to me<br>
&lt;kizu> Yep, ok with reverting<br>
&lt;JoshT> ... kizu was on thread and was OK with reverting and resolving properly later<br>
&lt;JoshT> ... we have an issue for resolving it later<br>
&lt;JoshT> RESOLVED: revert previous resolution<br>
</details>


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


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

Received on Wednesday, 15 October 2025 16:00:05 UTC