- From: Emilio Cobos Álvarez via GitHub <noreply@w3.org>
- Date: Wed, 01 Oct 2025 10:44:16 +0000
- To: public-css-archive@w3.org
That is, I agree in principle that making things work synchronously is nice if we can, but for these kind of "action-at-a-distance" effects is definitely more flexible to have a single point during the rendering steps where we recompute all the needed changes. Otherwise it gets kind of insane to reason about. For this particular thing I'm personally a bit on the fence, and it really depends on what kind of effect we / authors want. Doing it async allows us to do more complex / interesting computations and reuse the `IntersectionObserver` machinery, which I think is nice. Doing it sync is a bit trickier and restricts the amount of things we can check (what is currently on the spec should be doable tho). -- GitHub Notification of comment by emilio Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12732#issuecomment-3355749290 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 1 October 2025 10:44:17 UTC