14120 2011-09-13 03:49:59 +0000 Current spec for EventSource close method doesn't defined behaviour when close called after 'onopen' or 'onmessage'. For example, Google Chrome, closes connection if 'close' called while 'open' event dispatching and Opera doen't close it. 2011-09-19 03:26:27 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Server-Sent Events (editor: Ian Hickson) unspecified Other other RESOLVED INVALID http://www.whatwg.org/specs/web-apps/current-work/#top P3 normal --- 1 contributor ian annevk mike public-webapps vic99999 public-webapps-bugzilla oldest_to_newest 56687 0 contributor 2011-09-13 03:49:59 +0000 Specification: http://dev.w3.org/html5/eventsource/ Multipage: http://www.whatwg.org/C#top Complete: http://www.whatwg.org/c#top Comment: Current spec for EventSource close method doesn't defined behaviour when close called after 'onopen' or 'onmessage'. For example, Google Chrome, closes connection if 'close' called while 'open' method dispatching and Opera doen't close it. Posted from: 90.151.254.137 User agent: Opera/9.80 (Windows NT 5.1; U; ru) Presto/2.9.168 Version/11.51 56689 1 annevk 2011-09-13 05:52:48 +0000 How is it not defined? 56754 2 vic99999 2011-09-13 16:26:31 +0000 for example, event stream: data: 1 data: 2 data: 3 code: var es = new EventSource('stream'); es.addEventListener('open', function (event) { es.close(); }, false); es.addEventListener('message', function (event) { alert(event.data); es.close(); }, false); You will see different behavior for Chrome and Opera 56964 3 vic99999 2011-09-19 03:26:27 +0000 >> The close() method must close the connection, if any; must abort any reconnection attempt, if any; and must set the readyState attribute to CLOSED. If the connection is already closed, the method must do nothing. Sorry, didn't notice it in draft.