- From: Lea Verou <notifications@github.com>
- Date: Thu, 16 Sep 2021 08:56:45 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 16 September 2021 15:56:57 UTC
Hi @majido, @atanassov and I discussed this in our virtual f2f today. We are happy to see the [CSS WG resolution](https://github.com/w3c/csswg-drafts/issues/5321#issuecomment-910924409) that addresses the accessibility concerns. Looking at the proposed API, we thought that while referencing elements by explicit id is easy if the scroll-based animation involves e.g. header elements or the root element, it would be quite painful to use it for a collection of elements (e.g. a list of posts, products, places etc). Not only would that require setting individual ids on each one, but also adding a separate `@scroll-timeline` rule for each one even if the animation is exactly the same. Have you explored ways to reference a source element relative to the animation element? (e.g. keywords for common cases, or relative selectors, or `closest()` are some ideas that come to mind) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/521#issuecomment-921027219
Received on Thursday, 16 September 2021 15:56:57 UTC