Re: [csswg-drafts] [css-overflow-5] Limit scrolling to the associated scroll container when activating a marker (#11138)

The CSS Working Group just discussed `[css-overflow-5] Limit scrolling to the associated scroll container when activating a marker`, and agreed to the following:

* `RESOLVED: Only propagate the scroll into view for a scroll marker up to the common ancestor scroller of the targets`

<details><summary>The full IRC log of that discussion</summary>
&lt;andreubotella> flackr: when you have scroll markers as part of a control that are scrolling some scrollable area, it's not expected that scrolling that thing scrolls things outside it<br>
&lt;andreubotella> flackr: authors often expect that scrolling a container only scrolls inside that container<br>
&lt;kizu> q+<br>
&lt;fantasai> sgtm<br>
&lt;andreubotella> flackr: limit scrolling to the common scrolling container of the markers<br>
&lt;andreubotella> flackr: there are some related issues, but we don't have to discuss them here<br>
&lt;andreubotella> kizu: +1<br>
&lt;astearns> ack kizu<br>
&lt;andreubotella> kizu: one common case if we don't do this – a ToC that is a sidebar on mobile but on top on desktop, you don't want the scroll section to go back up<br>
&lt;andreubotella> PROPOSED RESOLUTION: Only propagate the scroll into view for a scroll marker up to the common ancestor scroller of the targets<br>
&lt;andreubotella> RESOLVED: Only propagate the scroll into view for a scroll marker up to the common ancestor scroller of the targets<br>
</details>


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


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

Received on Wednesday, 22 January 2025 16:30:05 UTC