- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Fri, 08 Nov 2024 19:52:05 +0000
- To: public-css-archive@w3.org
Since we have ideas that we might try to include all scroll-start-targets, we could consider something like `include`? Or, we could consider other values we may want to eventually support. E.g. if we wanted to eventually have options that align with / explain [scrolling to a fragment](https://html.spec.whatwg.org/#scrolling-to-a-fragment), we could consider what the names might be if we want to describe the ways that this is currently different from that and/or if we eventually wanted to be able to specify a scroll that was roughly equivalent to scrolling to a fragment. In particular, scrolling to a fragment: * Scrolls all ancestor scrollers as well, e.g. `scroll-start-target: none | local | global`? * Only scrolls if discovered during the navigation, but not if you later add the node to the document, e.g. `scroll-start-target: none | navigation | always` -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11173#issuecomment-2465641220 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 8 November 2024 19:52:06 UTC