Re: [csswg-drafts] [css-scroll-snap] Proposing `:snapped`: exposing private snapped item browser state for developers and designers (#6985)

thx! 🙂 

> So we'd need a narrower condition for breaking the loop at one iteration. 

I think https://github.com/w3c/csswg-drafts/issues/5979#issuecomment-899765136 is helpful for this. I could add details about the explained tight and loose cycles to the explainer? how it's not a tight cycle to maybe regret, but a loose one following the reputable `:hover` loop strategy?

> Also, does your answer also work for a hypothetical `:stuck` pseudo relating to `position: sticky`, as discussed in the FAQ?

We haven't discussed `:stuck` for a bit, but I'd love for it to follow `:snapped` footsteps 🤓 

-- 
GitHub Notification of comment by argyleink
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6985#issuecomment-1026489746 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 1 February 2022 05:23:25 UTC