I'm trying to update MessageEvent to match the current HTML5 spec.
Currently, MessageEvent has two references to MessagePort:
readonly attribute *MessagePort messagePort*;
void initMessageEvent(in DOMString typeArg, in boolean canBubbleArg,
in boolean cancelableArg, in DOMString
To be more precise, the HTML5 IDL defines the following:
typedef sequenceMessagePort MessagePortArray;
The types above are all MessagePortArray in the spec, not Array. So it seems
like the intent is that they should indeed get mapped to a vanilla JS Array.
I could make these attributes JS-only
Making this JS only for now seems fine. If we want to enable MessagePorts
for other binding languages we can define the mapping ourselves. For
example, for a sequence, the clear mapping for ObjC would be to NSArray*.
-Sam
On Wed, Aug 26, 2009 at 5:03 PM, Drew Wilson atwil...@google.com wrote:
On Aug 26, 2009, at 9:26 AM, Sam Weinig wrote:
Making this JS only for now seems fine. If we want to enable
MessagePorts for other binding languages we can define the mapping
ourselves. For example, for a sequence, the clear mapping for ObjC
would be to NSArray*.
I think ultimately we
On Wed, Aug 26, 2009 at 8:27 PM, Maciej Stachowiak m...@apple.com wrote:
On Aug 26, 2009, at 9:26 AM, Sam Weinig wrote:
Making this JS only for now seems fine. If we want to enable MessagePorts
for other binding languages we can define the mapping ourselves. For
example, for a sequence,
5 matches
Mail list logo
