- From: Antti Koivisto via GitHub <noreply@w3.org>
- Date: Wed, 01 Oct 2025 08:16:07 +0000
- To: public-css-archive@w3.org
> I see. I don't think that behavior is the best approach, because it will be slower (the browser will have to compute clips on every single forced layout) without any useful user or developer benefit that I can see. Updating the visibility during animation frame generation will still avoid the lagging across frames problem that [@fantasai](https://github.com/fantasai) (rightly) mentioned. WebKit (and Chrome?) currently implements force-hidden via an unobservable internal property but if it was implemented per spec as `visibility:force-hidden` then it would be quite observable: ``` anchor.style.visibility = "hidden"; alert(getComputedStyle(anchored).visibility); ``` I think it is pretty surprising in terms of how CSS generally works if that does not say "force-hidden". Developers expect all style effects to be synchronously available. -- GitHub Notification of comment by anttijk Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12732#issuecomment-3355241746 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 08:16:08 UTC