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 13717 - Clarify that a MessagePort clone, when created, hasn't been transfered, even if it was created as a result of another being transfered. ("If any object is listed in transfer more than once, or any of the Transferable objects listed in transfer have alread
Summary: Clarify that a MessagePort clone, when created, hasn't been transfered, even ...
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: Web Messaging (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: public-webapps-bugzilla
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-09 21:10 UTC by contributor
Modified: 2011-10-19 00:09 UTC (History)
3 users (show)

See Also:

Attachments

Description contributor 2011-08-09 21:10:33 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/complete.html
Multipage: http://www.whatwg.org/C#posting-messages
Complete: http://www.whatwg.org/c#posting-messages

Comment:
Clarify that a MessagePort clone, when created, hasn't been transfered, even
if it was created as a result of another being transfered. ("If any object is
listed in transfer more than once, or any of the Transferable objects listed
in transfer have already been transfered once before, then throw a
DATA_CLONE_ERR exception and abort these steps" is confusing)

Posted from: 216.239.45.4 by ian@hixie.ch
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_5_8) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.29 Safari/535.1
Comment 1 Ian 'Hixie' Hickson 2011-10-07 22:00:12 UTC 
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.
Comment 2 contributor 2011-10-07 22:01:55 UTC 
Checked in as WHATWG revision r6653.
Check-in comment: Clarify that you can transfer a port more than once by avoiding confusing terminology that suggested otherwise.
http://html5.org/tools/web-apps-tracker?from=6652&to=6653
Comment 3 contributor 2011-10-19 00:09:20 UTC 
Checked in as WHATWG revision r6696.
Check-in comment: Clarify that you can transfer a port more than once by avoiding confusing terminology that suggested otherwise. (see also r6653)
http://html5.org/tools/web-apps-tracker?from=6695&to=6696