- From: vmpstr via GitHub <sysbot+gh@w3.org>
- Date: Wed, 20 Mar 2024 15:30:35 +0000
- To: public-css-archive@w3.org
The second resolution isn't what I was thinking about initially. I think it's a good one, but there are a couple of cases: 1. Anchored element (`A`) and positioned element (`P`) are both relevant to the user, then a. `A`'s container with c-v auto is scrolled offscreen -- it should still remain relevant b. `P`'s container with c-v auto is scrolled offscreen -- it should still remain relevant c. Both `A`'s and `P`'s containers are scrolled off screen -- not sure if things should stay relevant? 2. `A` is not relevant to the user, so its `anchor-name` should not be discoverable 3. `P` is not relevant to the user -- I don't think it should become relevant, since then we'd need to know it's being positioned I propose spending a few minutes thinking through all of the cases here, since I want to avoid to accidentally requiring rendering in an otherwise skipped subtree -- GitHub Notification of comment by vmpstr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10040#issuecomment-2009852473 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 20 March 2024 15:30:36 UTC