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 23011 - MessageEventInit source member cannot be a MessagePort
Summary: MessageEventInit source member cannot be a MessagePort
Status: RESOLVED FIXED
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:
: 23012 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-08-19 19:38 UTC by contributor
Modified: 2013-08-20 17:50 UTC (History)
3 users (show)

See Also:

Attachments

Description contributor 2013-08-19 19:38:58 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/comms.html
Multipage: http://www.whatwg.org/C#event-definitions-2
Complete: http://www.whatwg.org/c#event-definitions-2
Referrer: 

Comment:
MessageEventInit source member cannot be a MessagePort

Posted from: 63.166.115.40
User agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0
Comment 1 Chris Dumez 2013-08-19 19:40:09 UTC 
*** Bug 23012 has been marked as a duplicate of this bug. ***
Comment 2 Chris Dumez 2013-08-19 19:41:41 UTC 
In http://www.whatwg.org/specs/web-apps/current-work/multipage/comms.html#messageeventinit, source can only be a Window. However, in the MessageEvent interface, it can be either a Window or a MessagePort. Was this done on purpose or was the dictionary member simply missed in the update?
Comment 3 contributor 2013-08-20 17:50:07 UTC 
Checked in as WHATWG revision r8148.
Check-in comment: Make sure you can create a MessageEvent object with a MessagePort as a source.
http://html5.org/tools/web-apps-tracker?from=8147&to=8148