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

flackr has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-overflow-5] Limit scrolling to the associated scroll container when activating a marker ==
Currently, when a scroll marker is activated, the [activation behavior](https://drafts.csswg.org/css-overflow-5/#scroll-marker-activation) [scrolls the scroll target into view](https://drafts.csswg.org/cssom-view-1/#scroll-a-target-into-view). This behavior right now will scroll every scrolling box up to the root to the target.

I think that it is quite common to expect that the scroll stops at the managed scroll container. E.g. @bakura10 from twitter mentioned this expectation in https://github.com/w3c/csswg-drafts/issues/9452#issuecomment-1756829797. In #9452 I proposed adding this option to the scroll into view api.

The question here is, should we restrict the scroll into view for activation to stop at the [scroll marker group container](https://drafts.csswg.org/css-overflow-5/#scroll-marker-group-container)? This would mean that we would not ensure that the group container is currently scrolled into view in all of it's ancestor scrolling containers.

If we don't restrict this, you could end up in a degenerate situation when the scroll markers are above the targeted [scroll marker group container](https://drafts.csswg.org/css-overflow-5/#scroll-marker-group-container) as scrolling the ancestors of the group container to position the group container into view would naturally scroll the markers out of view.

I propose we do this.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11138 using your GitHub account


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

Received on Friday, 1 November 2024 13:54:14 UTC