On Wed, May 25, 2022 at 10:49 PM Chris Harrelson <[email protected]> wrote:
> > > On Wed, May 25, 2022 at 1:44 PM Philip Jägenstedt <[email protected]> > wrote: > >> It looks like the TAG was prodded, since the "2022-06-13-week" >> milestone was just added to >> https://github.com/w3ctag/design-reviews/issues/734. >> >> However, I don't think it's reasonable for us to keep waiting for the >> TAG until mid-June when this proposal already had plenty of input from >> other vendors in https://github.com/w3c/csswg-drafts/issues/6850. >> >> This API checks the synchronously available state to determine if the >> element is going to be hidden in the next frame, but it doesn't >> determine if it's really visible like Intersection Observer. That >> seems like a useful thing to have. > > > The useful thing is: > * Reliably detect visibility according to some basic semantics that are > common to test for (use cases listed in the issue) > * Provide a performant way to detect content-visibility:hidden > > >> However, the bits involving inert >> and aria-hidden do seem a bit out of place for something called >> isVisible, to me. >> > > These two are no longer part of the proposal. > Inert still is, see https://drafts.csswg.org/cssom-view/#dom-element-isvisible. Was there agreement to drop that, but it didn't happen yet? -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAARdPYcddqB%2B4ee7Tsh1Ss%3DkVE%2B5bFMjWaU%3DMaQKzpg9ukBTgA%40mail.gmail.com.
