- From: Xiaocheng Hu via GitHub <sysbot+gh@w3.org>
- Date: Wed, 21 Jun 2023 21:57:22 +0000
- To: public-css-archive@w3.org
Another idea: do we really need to expose `anchor-scroll` to developers? Especially now it defaults to the default/implicit anchor element, and there really doesn't seem to be any legit use case of `anchor-scroll: none` Maybe we can just keep it as an internal detail of calculating the snapshotted scroll offset that: - If the element has a default anchor element that is acceptable, use that element - Otherwise, if the element has an implicit anchor element that is acceptable, use that element - Otherwise, use some anchor element from some `anchor()` or `anchor-size()` (with some rules when multiple anchors are used) This only makes the behavior less controllable (for a developer) when using multiple anchors in different scrollers; But again, the current `anchor-scroll` is already broken in this case -- GitHub Notification of comment by xiaochengh Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8675#issuecomment-1601735010 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 21 June 2023 21:57:24 UTC