- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Thu, 22 Aug 2024 20:05:09 +0000
- To: public-css-archive@w3.org
From https://github.com/w3c/csswg-drafts/issues/10711#issuecomment-2302563007 > emilio: Is overflow the only place we want to support this use-case ? > emilio: author might want this for stuff in the screen @emilio I think that fundamentally there are two shapes this property could take represented by options 1 and 2. In the first case the author explicitly styles which things are inert, and in the latter they apply a style that tries to automate when things need to change states for them. As @tabatkins mentioned they're not necessarily mutually exclusive, but option 2 is trying to handle the common easily detectable cases. If you have any thoughts for things we might be able to do to cover the other use cases you mentioned in an automated way i'd welcome improvements to how option 2 works, but the general question of whether something is visible seems non-trivial to compute. If it's not automatically detectable then it would require a solution like option 1 where the author styles the content inert regardless of its location. If we don't also have an automated option then this adds an additional burden on developers creating scrolling experiences to ensure that they have some way of updating this as the user scrolls changing the current content. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10711#issuecomment-2305537765 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 22 August 2024 20:05:10 UTC