- From: Chris Harrelson via GitHub <noreply@w3.org>
- Date: Wed, 01 Oct 2025 17:04:52 +0000
- To: public-css-archive@w3.org
> then it would be quite observable I agree that it is observable in general, such as in the example you gave (if a browser implemented the `force-hidden` value per the current specification. [Aside: maybe we should just remove that line in the spec though--is it actually useful?]). I see your point about the style being "stale" if the visibility computed by the browser is not done until the next animation frame, and this update is considered part of style recalc. However, I see `position-visibility` visibility computation as a "UA behavior that is observable afterwards" rather than "letting style be stale until the next frame". Like Emilio said, there are other examples of UA behavior like (especially related to scroll--a UA behavior). You can also compare it to the [last-successful-position](https://drafts.csswg.org/css-anchor-position-1/#last-successful-position-option) part of the spec, which also computes at `ResizeObserver` timing as I'm proposing for `position-visibility` checks. The last-successful-position-feature affects the preferred position-try fallback for subsequent frames. Note: Blink recomputes chosen position-try fallbacks on every layout, including forced layouts. -- GitHub Notification of comment by chrishtr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12732#issuecomment-3357310201 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 17:04:53 UTC