EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Did Not Understand Request
Change Description: no spec change
Rationale: Why would they be?

"message" and "open" events will fire even after calling "eventSource.close()"

XMLHttpRequest#abort(), opposite, clears task in tasks queue to fire "readystatechange"

I guess we can clear them, but that just means we're discarding  events that were received before the close() method was called (even though they're being fired after).

Indeed, I think firing messages after .close() is called is much more likely to cause bugs than provide value. I don't think most authors think about these things in terms of several threads sending asynchronous messages to each other, and more in the terms of a single thread where everything is happening.

Fair enough. Will do.

anyway,
calling stop() while event dispatching will not prevent other event handlers calling
but i think, that it's better to make "close()" behavior to be more similar to XMLHttpRequest#abort() and WebSockets#close()

Note that WebSocket.close() doesn't do this either. Changing that would contradict the protocol spec: WebSockets is explicitly designed to allow you to close the connection before you've finished receiving everything you're going to get; there's a clearly defined end handshake.

I've fixed this for EventSource though.

Checked in as WHATWG revision r6688.
Check-in comment: Make EventSource.close() cause the events to stop firing even if they're already queued.
http://html5.org/tools/web-apps-tracker?from=6687&to=6688

what about "open" and "error" events?
It seems, they should also be dropped...

Seems easier to just empty the "remote event task source".

Emptying the task source is a bit dodgy because you'd have to make sure to only empty the tasks that were fired for this specific EventSource object. You also have to make sure that no new tasks get queued.

Agreed that 'open' events shouldn't fire, though. In particular, as specced, if you call close() between the connection being open and the 'open' event firing, the object will end up in the wrong state. A similar problem exists for 'error', but it's actually worse; if the connection closes just before you call close(), per spec, the connection will actually be reopened! I'll fix that.

That is what XMLHttpRequest does and HTML media elements do. E.g. from HTML:

"If there are any tasks from the media element's media element event task source in one of the task queues, then remove those tasks."

I used that language for XMLHttpRequest.

It works for media elements because each one has its own task source.

Oh I see, it seems it would be simple to do the same for EventSource. I should update XMLHttpRequest to say the task source is per object.

EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Accepted
Change Description: see diff given below
Rationale: Concurred with reporter's comments.

Checked in as WHATWG revision r6772.
Check-in comment: Make sure once you call closed() that EventSource objects stay down.
http://html5.org/tools/web-apps-tracker?from=6771&to=6772