- From: Yehonatan Daniv via GitHub <sysbot+gh@w3.org>
- Date: Mon, 12 Jun 2023 09:11:49 +0000
- To: public-css-archive@w3.org
> Is that the reason the in-view selector was dismissed? There was a specific section on this in the CSSWG wiki but can't find it now cause the wiki is down ): But essentially it said this would be problematic in cases where you could select based on this state, and then undo that state inside the same rule. I should note that a sort of an `in-view` state is also being considered for `state()` queries, which may also be useful for other use-cases, like for having different elements for checking state and applying style change. > I know in the very very early days of the scroll-driven animations spec we have scroll triggers which would have been awesome--basically like declarative intersection observer so you could trigger transitions or even just static changes Yes, there was such issue (couldn't find it) but we agreed that "scroll-driven" is technically and conceptually different from "scroll-trigger". So we closed that one. Having a declarative intersection observer would be great, but since it was stuck I'm trying here to find a way forward and also addressing specific cases for triggering animations. > I think it would be worth considering other options before we try to overload them for this Understood, they may be completely orthogonal to this case, just trying to consider sensible defaults. -- GitHub Notification of comment by ydaniv Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8942#issuecomment-1586923345 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 12 June 2023 09:11:50 UTC