Re: [w3ctag/design-reviews] WG New Spec: Scroll-Triggered Animations (Issue #1167)

matatk left a comment (w3ctag/design-reviews#1167)

Thanks @DavMila and @astearns for your review request and further info. We are happy to see the work continue, and to close this review.

However, whilst we appreciate the importance of consistency with respect to `contain` and `cover`, having been introduced in scroll-driven animations, and in general we agree that the terms are likely not universally confusing, we are concerned about how CSS (and other groups) can get reliable input from developers on what they find confusing, as specs evolve. We think it most likely that, particularly with minor-to-moderate things that confuse developers, most _aren't_ likely to report those issues as bugs on the spec.

This is of course a key issue that we all need to work to address - ensuring we're reaching the [second-highest-priority constituency [link for readers new to W3C]](https://www.w3.org/TR/design-principles/#priority-of-constituencies) - though with near-universally deployed specs such as CSS it is of course amplified.

If there's anything you think we could do as a community, perhaps kicking of with a TPAC breakout on how to ensure we're getting feedback as inclusively as possible, please let us know.

Finally, we've recently discovered a case where scroll-driven animations can be used to create a scroll spy that can make network requests based on scroll positioning, even when JavaScript is disabled. This opens up privacy concerns, we believe that the same issue applies to scroll triggered animations and would be interested in the CSSWG's thinking on this.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1167#issuecomment-5202837946
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1167/5202837946@github.com>