Re: [csswg-drafts] [css-contain] content-visibility: auto visibility check timing needs details (#8542)

@vmpstr the algorithm changes we were going for (see https://github.com/w3c/csswg-drafts/pull/8704) for these other extra passes were intended to only allow a single extra pass. I think rather than having each step recalculate styles and layout I'd would rather have a single additional pass if either of the things changed. This means language more like:

1. If there are stale animation timelines or there are content-visibility elements with undetermined visibility:
   1. Recalculate styles and update layout for doc.

I also think for scroll driven animations (and possibly this case as well), that it may make more sense to run after ResizeObserver as that is the time developers typically size / position sub-components based on ancestor components so it is likely to introduce visible content.

-- 
GitHub Notification of comment by flackr
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8542#issuecomment-1529732137 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 1 May 2023 13:52:30 UTC