IntersectionObserver's delay/trackVisibility and IntersectionObserverEntry's isVisible missing from main spec

[foolip]

https://w3c.github.io/IntersectionObserver/v2/ has a number of additions compared to https://w3c.github.io/IntersectionObserver/ which are shipped in at least some browsers, but https://w3c.github.io/IntersectionObserver/ (and https://www.w3.org/TR/intersection-observer/) are much more discoverable.

Is it time to promote https://w3c.github.io/IntersectionObserver/ to v2 so that the most up-to-date spec is more easily found?

Background: I was here to file issues about certain attributes not being in the spec, and found the v2 spec only after reading through Intent to Ship: IntersectionObserver V2.

[foolip]

Hmm, but looking at https://w3c.github.io/IntersectionObserver/v2/#idl-index and the date, it seems like v2 isn't the version of the spec being maintained.

For clarity, members that are missing from https://w3c.github.io/IntersectionObserver/ are IntersectionObserver.prototype.delay, IntersectionObserver.prototype.trackVisibility and IntersectionObserverEntry.prototype.isVisible. I'll rename the issue to make it clear that's the point of this.

cc @szager-chromium

[astearns]

"Shipped in at least some browsers" seems to be just Blink.

https://caniuse.com/intersectionobserver-v2

I haven’t found the place where these things were even proposed to other browsers. Looks like we need to re-start the process for these.

[foolip]

What's the status of this?

The TAG and Mozilla were made aware of this proposal here:
mozilla/standards-positions#109
w3ctag/design-reviews#328

https://github.com/WebKit/standards-positions did not exist at the time.

The feature is used by over 6% of Chrome page loads by now:
https://chromestatus.com/metrics/feature/timeline/popularity/3051

[BasixKOR]

Also opened an issue there: szager-chromium#8

Leaving this link for future reference.

[dontcallmedom]

#523 seems to be addressing this FTR