Improve the declared IDL type for postMessage()'s transferables

Improve the declared IDL type for postMessage()'s transferables

Make the postMessage() IDL type for the transferables argument be
equal to what the specs and the custom binding code actually
supports. That is, a sequence of Transferables.

Accurately defining the Transferable typedef is dependent on better
union type support (http://crbug.com/240176); provide an incomplete 
typedef until that is in place.

R=haraken@chromium.org,jsbell@chromium.org
BUG=393245
Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=178322

[sof, 2014-07-16 15:31:23]

Please take a look.

[haraken, 2014-07-16 16:02:12]

LGTM

[jsbell, 2014-07-16 16:48:08]

lgtm, but can we use sequence<> to match the specs?

https://codereview.chromium.org/393353003/diff/1/Source/core/dom/MessagePort.idl
File Source/core/dom/MessagePort.idl (right):

https://codereview.chromium.org/393353003/diff/1/Source/core/dom/MessagePort....
Source/core/dom/MessagePort.idl:32: 
Nit: remove this whitespace?

(Could just be a glitch in the review tool)

https://codereview.chromium.org/393353003/diff/1/Source/core/dom/MessagePort....
Source/core/dom/MessagePort.idl:33: [Custom, RaisesException] void
postMessage(any message, optional Transferable[] transfer);
It appears to be sequence<Transferable> in specs rather than Transferable[].

[sof, 2014-07-16 18:19:15]

Thanks for the reviews.

https://codereview.chromium.org/393353003/diff/1/Source/core/dom/MessagePort.idl
File Source/core/dom/MessagePort.idl (right):

https://codereview.chromium.org/393353003/diff/1/Source/core/dom/MessagePort....
Source/core/dom/MessagePort.idl:32: 
On 2014/07/16 16:48:08, jsbell wrote:
> Nit: remove this whitespace?
> 
> (Could just be a glitch in the review tool)

It's real, but unintentional. Removed now.

https://codereview.chromium.org/393353003/diff/1/Source/core/dom/MessagePort....
Source/core/dom/MessagePort.idl:33: [Custom, RaisesException] void
postMessage(any message, optional Transferable[] transfer);
On 2014/07/16 16:48:08, jsbell wrote:
> It appears to be sequence<Transferable> in specs rather than Transferable[].

Yes, that it is. Let's mirror that; supported by extractTransferables() after
all.

[sof, 2014-07-16 18:28:55]

The CQ bit was checked by sigbjornf@opera.com

[commit-bot: I haz the power, 2014-07-16 18:29:52]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/sigbjornf@opera.com/393353003/20001

[sof, 2014-07-16 21:38:15]

The CQ bit was unchecked by sigbjornf@opera.com

[sof, 2014-07-16 21:38:36]

The CQ bit was checked by sigbjornf@opera.com

[commit-bot: I haz the power, 2014-07-16 21:39:43]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/sigbjornf@opera.com/393353003/20001

[commit-bot: I haz the power, 2014-07-17 05:07:07]

Change committed as 178322