[MutationObservers] Clear pending mutation records on disconnect()

• Component: DOM
• Status: RESOLVED FIXED

[Rafael Weinstein]

It's pretty strange to call disconnect() and still *possibly* get one invocation of your callback. We should just clear any pending deliveries.

It's possible that script way want to know immediately prior to calling disconnect() *what* mutation records are pending delivery. If this happens in practice, we can add a method to synchronously retrieve & clear pending mutation records.

[Ryosuke Niwa]

What does the spec says?

[Adam Klein]

(In reply to comment #1)
> What does the spec says?

The spec matches the current behavior. Once the text is part of DOM4 (annevk said he was going to patch it in this week), we'll open a bug there too.

This bug should be seen as depending on the spec change.

[Ryosuke Niwa]

(In reply to comment #2)
> The spec matches the current behavior. Once the text is part of DOM4 (annevk said he was going to patch it in this week), we'll open a bug there too.
> 
> This bug should be seen as depending on the spec change.

Okay. Could you guys start a new thread or reply to an existing thread about this? I would be interested to hear what Jonas and Olli have to say about this.

[Adam Klein]

(In reply to comment #3)
> (In reply to comment #2)
> > The spec matches the current behavior. Once the text is part of DOM4 (annevk said he was going to patch it in this week), we'll open a bug there too.
> > 
> > This bug should be seen as depending on the spec change.
> 
> Okay. Could you guys start a new thread or reply to an existing thread about this? I would be interested to hear what Jonas and Olli have to say about this.

As noted above, my plan is to file this as a bug against the spec once the initial spec text is checked in. I asked Raf to file this bug since we were just talking about it and I didn't want it to get lost.

[Ryosuke Niwa]

(In reply to comment #4)
> As noted above, my plan is to file this as a bug against the spec once the initial spec text is checked in. I asked Raf to file this bug since we were just talking about it and I didn't want it to get lost.

Okay. That makes sense.

[Adam Klein]

(In reply to comment #5)
> (In reply to comment #4)
> > As noted above, my plan is to file this as a bug against the spec once the initial spec text is checked in. I asked Raf to file this bug since we were just talking about it and I didn't want it to get lost.
> 
> Okay. That makes sense.

https://www.w3.org/Bugs/Public/show_bug.cgi?id=16092

[Adam Klein]

Created attachment 129100 [details]
Patch

[WebKit Review Bot]

Comment on attachment 129100 [details]
Patch

Clearing flags on attachment: 129100

Committed r109058: <http://trac.webkit.org/changeset/109058>

[WebKit Review Bot]

All reviewed patches have been landed.  Closing bug.