David: Wanted to follow-up on an rather involved issue--but haven't followed up yet.

Alex: fine with kicking down the road.

Peter: how long?

David: perhaps move to the F2F.

David: I think one of the problems was that they were inserting stuff into a list that different people interpreted this differently. The issue I believe is attempting to specify this better.

Alex: Probably worth checking across implementations...turns out there are several; Edge, Gecko, Blink.

David: The details that I mentioned might not be interoperable but not many may notice; but it would be good to have this interoperable

Peter: Next steps?

David: I'll look into this this week and revisit next wee

Alex: I have not discussed with Zager

Dan: Shall I bump this in that case?

Dan: It is sooo bumped! OK

David: some of this was to remind me to do stuff and i haven't done the stuff yet.

Peter: [bumping 2 weeks]

Kenneth: BTW this just landed in safari tech preview https://bugs.webkit.org/show_bug.cgi?id=159475

David: we just got a separate review request for v2

David: Two remaining issues - one falls back to the task scheduling issue (72). The other one was Peter's concern about string based APIs.

Peter: i think they fixed the string based APIs issue..

David: punt 4 weeks

Rossen: This is a shipped feature... what's remaining.

David: Specifying what's actually shipped and if it is interoperable. My concern was that the HTML event loop spec is not specified clearly enough and not very interoperable. So then, how intersection observer fits into all of this. I recall writing one event loop test and that failed everywhere. Don't think keeping the issue open is going to do anything else other than nag me to look at it.

Peter: Specifying the event loop has been a long time coming :) and not there still.

Rossen: So what's really remaining for TAG here?

David: I'm OK closing this one and file a separate issue for tracking the specific dependencies between intersection observer and the event loop