Discussion:
Update on Intersection Observer?
Léonie Watson
2018-03-26 23:46:28 UTC
Permalink
Stefan,

Could you share an update with the WG? When we last spoke, you were
hoping to handle the open PRs and substantive issues during the first
quarter of the year.
--
@LeonieWatson @***@toot.cafe Carpe diem
Léonie Watson
2018-06-04 16:53:08 UTC
Permalink
Post by Léonie Watson
Stefan,
Could you share an update with the WG? When we last spoke, you were
hoping to handle the open PRs and substantive issues during the first
quarter of the year.
Ping?
--
@LeonieWatson @***@toot.cafe Carpe diem
Stefan Zager
2018-06-08 22:26:58 UTC
Permalink
Sorry for the delay. I made another pass through the bug tracker this week.

There are still a few places where the spec needs updated language for
clarity; I'm working my way through them. In the bug tracker, I marked
those issues with the label "needs spec".

There are a handful of feature requests that I believe we should punt on
for now, in the interest of moving forward with a spec that most browsers
already implement. I marked those bugs with the "v2" label.

And there is one issue that probably needs to be resolved before moving
forward:

Should the implicit root be the layout viewport or the visual viewport?
Should that be a configurable option? If so, what should the default be?

https://github.com/w3c/IntersectionObserver/issues/95
Post by Léonie Watson
Stefan,
Could you share an update with the WG? When we last spoke, you were
hoping to handle the open PRs and substantive issues during the first
quarter of the year.
--
@LeonieWatson @***@toot.cafe Carpe diem
Léonie Watson
2018-06-23 19:16:48 UTC
Permalink
Post by Stefan Zager
Sorry for the delay. I made another pass through the bug tracker this week.
Thanks Stefan.
Post by Stefan Zager
There are still a few places where the spec needs updated language for
clarity; I'm working my way through them. In the bug tracker, I marked
those issues with the label "needs spec".
It looks like there are four such issues remaining [1]. any estimate on
when they'll be resolved?
Post by Stefan Zager
There are a handful of feature requests that I believe we should punt on
for now, in the interest of moving forward with a spec that most
browsers already implement. I marked those bugs with the "v2" label.
Makes sense.
Post by Stefan Zager
And there is one issue that probably needs to be resolved before moving
Should the implicit root be the layout viewport or the visual viewport?
Should that be a configurable option? If so, what should the default be?
https://github.com/w3c/IntersectionObserver/issues/95
Is there anything I/we can do to help find a resolution for this one?
Happy to reach out to other WG and/or people if it would help.

Léonie
[1] https://github.com/w3c/html/pull/1489
Post by Stefan Zager
Stefan,
Could you share an update with the WG? When we last spoke, you were
hoping to handle the open PRs and substantive issues during the first
quarter of the year.
--
@LeonieWatson @***@toot.cafe Carpe diem
--
@LeonieWatson @***@toot.cafe Carpe diem
Loading...