- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 22 Jun 2023 00:37:23 +0000
- To: public-css-archive@w3.org
> But that means scrolling will break for sure when "doing something special", including all use cases that involve multiple anchor elements, which is still an important use case we want to support. That's fine, you can still *set* `anchor-default` and then just manually specify all your anchors. Or use `anchor-default` for your "main" anchor (which'll be recommended by tutorials, I assume) and manually specify the rest. > For example, find the lexicographically first property with an anchor() or anchor-size(), and then use the anchor element in the first anchor function there. That's exactly the sort of unpredictability I'm talking about. Switching from setting 'top' to setting 'bottom' can change whether or not an `anchor()` in 'left' gets used for the scroll adjustment or not. It's deterministic, but with no author-facing rhyme or reason behind it; we just set up a completely arbitrary ordering that they can't predict without reading the spec. For an example of a predictable behavior, we could go with "if all your anchor() functions are for the same target element, use that as the scroll adjuster". This would handle the most common case in a predictable and useful way, but it would cause scroll adjustment to break if they anchored to a second element, especially if they only did it sometimes, like in a fallback. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8675#issuecomment-1601859854 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 22 June 2023 00:37:25 UTC