- From: Rune Lillesveen via GitHub <sysbot+gh@w3.org>
- Date: Wed, 30 Apr 2025 07:10:31 +0000
- To: public-css-archive@w3.org
> I feel like we should avoid propagation if possible here (that's our general policy, after all), and just say that if nothing else catches the scroll-state() query, it's answered by the viewport.
Maybe propagate is not the right term, but we do apply scroll-snap-type from root to viewport: https://drafts.csswg.org/css-scroll-snap/#scroll-snap-type
In that case we don't have an alternative way, I guess.
> So this would mean that Rune's code wouldn't work as intended (as the root element is capturing the scroll-state query), but if you removed the :root { container-type: scroll-state; } rule then it would Just Work by default. That seems like a good behavior to me.
Isn't that a bit of a trap for authors? That setting scroll-state on the root element stops scroll-state() queries on the viewport from working?
--
GitHub Notification of comment by lilles
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11542#issuecomment-2841025953 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 30 April 2025 07:10:32 UTC