23011 2013-08-19 19:38:58 +0000 MessageEventInit source member cannot be a MessagePort 2013-08-20 17:50:07 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#event-definitions-2 P3 normal Unsorted 1 contributor ian chris ian mike contributor oldest_to_newest 92281 0 contributor 2013-08-19 19:38:58 +0000 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 92284 1 chris 2013-08-19 19:40:09 +0000 *** Bug 23012 has been marked as a duplicate of this bug. *** 92285 2 chris 2013-08-19 19:41:41 +0000 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? 92360 3 contributor 2013-08-20 17:50:07 +0000 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