- From: vmpstr via GitHub <sysbot+gh@w3.org>
- Date: Wed, 08 Mar 2023 16:06:32 +0000
- To: public-css-archive@w3.org
I was thinking more about this: I think the language in the spec should change to say that it is in fact the first visibility computation that needs to be synchronous -- if it results in changes to the skipped state, those changes need to be incorporated into the presented frame by re-computing rendering synchronously. This is different from what the spec says, since it's fine to let the _second_ computation to be asynchronous even if that second computation happens as a result of re-computing rendering due to the first computation. I'm guessing that's the worry here: that we may construct a page where the state is unstable (e.g. #8407), so we still want to make progress. The way the text is phrased right now implies that the stable state needs to be found in the same frame as c-v was first discovered. -- GitHub Notification of comment by vmpstr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8542#issuecomment-1460418890 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 8 March 2023 16:06:34 UTC