- From: Johannes Odland via GitHub <sysbot+gh@w3.org>
- Date: Fri, 10 Nov 2023 15:57:09 +0000
- To: public-css-archive@w3.org
There is another use case for an additional value here: The premise for `auto` is that the user agent knows when an element is relevant for the user. That is not always true, and it would be great if authors were able to tell the user agent when it is relevant or not. If an element is in the viewport it is considered to be relevant, and is its content is not skipped, while It could be in the viewport, only obscured. Scroll-driven animations opens up new opportunities. As an example, we could break down an article in “pages” and stack them on top of each other visually. As the user scrolls we could animate each page off the top of the stack, as if they were shoving the paper off the stack. In this example every element on the page would be in the viewport, but only a few on the top would be relevant to the user. Authors should be able to tell the user agent to skip that content, while ensuring that the content is available as usual to user anger features such as find-in-page and so on. -- GitHub Notification of comment by johannesodland Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9579#issuecomment-1805995208 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 10 November 2023 15:57:11 UTC