14660 2011-11-01 16:48:17 +0000 [Editorial] Clarification for CLOSING in Garbage Collection 2011-11-02 20:46:36 +0000 1 1 1 Unclassified WebAppsWG WebSocket API (editor: Ian Hickson) unspecified PC Windows NT RESOLVED WORKSFORME P2 normal --- 1 brian.raymor ian ian mike public-webapps public-webapps-bugzilla oldest_to_newest 59419 0 brian.raymor 2011-11-01 16:48:17 +0000 Since the W3C WebSocket API was clarified to reflect that onmessage is only called during the OPEN readyState (14474 - Make it possible to close a connection in such a manner that all subsequent events are suppressed), there are corresponding editorial changes required in Section 9 Garbage Collection: A WebSocket object whose readyState attribute's value was set to OPEN (1) or CLOSING (2) as of the last time the event loop started executing a task must not be garbage collected if there are any event listeners registered for message events, error, or close events. should differentiate between OPEN and CLOSING: A WebSocket object whose readyState attribute's value was set to OPEN (1) as of the last time the event loop started executing a task must not be garbage collected if there are any event listeners registered for message events, error, or close events. A WebSocket object whose readyState attribute's value was set to CLOSING (2) as of the last time the event loop started executing a task must not be garbage collected if there are any event listeners registered for error or close events. 59525 1 ian 2011-11-02 20:46:36 +0000 This has already been fixed.