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 24058 - Rather than disentangling the two ports when one port suffers a catastrophy, just mark the ports as ill-fated and have some attribute that exposes ill-fatedness, so that you can tell if you were send an ill-fated port.
Summary: Rather than disentangling the two ports when one port suffers a catastrophy, ...
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-12-10 23:47 UTC by contributor
Modified: 2013-12-11 19:55 UTC (History)
2 users (show)

See Also:

Attachments

Description contributor 2013-12-10 23:47:55 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/
Multipage: http://www.whatwg.org/C#transferMessagePort
Complete: http://www.whatwg.org/c#transferMessagePort
Referrer: 

Comment:
Rather than disentangling the two ports when one port suffers a catastrophy,
just mark the ports as ill-fated and have some attribute that exposes
ill-fatedness, so that you can tell if you were send an ill-fated port.

Posted from: 216.239.45.74 by ian@hixie.ch
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1729.3 Safari/537.36
Comment 1 Ian 'Hixie' Hickson 2013-12-11 19:55:34 UTC 
An attribute wouldn't work, you'd have to do sync IPC to set it up before script could get to it. But we can fire an event.