This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 20739 - If the MessagePort fired a 'disconnected' method when the other side goes away, then the array of MessagePort objects could be cleaned up and we would not need PortCollection.
Summary: If the MessagePort fired a 'disconnected' method when the other side goes awa...
Status: RESOLVED WONTFIX
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-22 20:33 UTC by contributor
Modified: 2013-03-15 22:43 UTC (History)
2 users (show)

See Also:

Attachments

Description contributor 2013-01-22 20:33:28 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/web-messaging.html
Multipage: http://www.whatwg.org/C#broadcasting-to-many-ports
Complete: http://www.whatwg.org/c#broadcasting-to-many-ports

Comment:
If the MessagePort fired a 'disconnected' method when the other side goes
away, then the array of MessagePort objects could be cleaned up and we would
not need PortCollection.

Posted from: 24.6.118.245
User agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.27 (KHTML, like Gecko) Chrome/26.0.1384.2 Safari/537.27
Comment 1 Ian 'Hixie' Hickson 2013-03-15 22:43:02 UTC 
Yeah, but that would expose garbage collection timings, which we don't want to do.