Fix generator to use SerializedScriptValue for all postMessages

Fix generator to use SerializedScriptValue for all postMessages

BUG=

Committed: https://github.com/dart-lang/sdk/commit/e67b4c916179aae334ab7458a857d39ac8867379

[terry, 2016-02-23 14:19:03]

terry@google.com changed reviewers:
+ terry@google.com

[terry, 2016-02-23 14:19:04]

https://codereview.chromium.org/1723703002/diff/1/tools/dom/scripts/generator.py
File tools/dom/scripts/generator.py (right):

https://codereview.chromium.org/1723703002/diff/1/tools/dom/scripts/generator...
tools/dom/scripts/generator.py:730: 'any set _DOMWindowCrossFrame.postMessage':
_serialize_SSV,
I'm wondering how the tests ran on integration w/o any problems.

Do we need to add postMessage for ServieWorkerClient?

There are some other like CrossOriginServiceWorker (I guess that's
_DOMWindowCrossFrame)?

What about postMessage in CompositeWorkerGlobalScope?

Noticed we never did this for ServiceWorker in 39/45 there is a postMessage
shouldn't that have been there too?

There is a postMessage in ServicePort for 45 should that be here too?

And what about Worker it was in 39 and there's still a postMessage in 45?

[Alan Knight, 2016-02-23 17:28:59]

Description was changed from

==========
Fix generator to use SerializedScriptValue for all postMessages

BUG=
==========

to

==========
Fix generator to use SerializedScriptValue for all postMessages

BUG=

Committed:
https://github.com/dart-lang/sdk/commit/e67b4c916179aae334ab7458a857d39ac8867379
==========

[Alan Knight, 2016-02-23 17:29:00]

Committed patchset #2 (id:20001) manually as
e67b4c916179aae334ab7458a857d39ac8867379 (presubmit successful).

[Alan Knight, 2016-02-23 17:54:37]

https://codereview.chromium.org/1723703002/diff/1/tools/dom/scripts/generator.py
File tools/dom/scripts/generator.py (right):

https://codereview.chromium.org/1723703002/diff/1/tools/dom/scripts/generator...
tools/dom/scripts/generator.py:730: 'any set _DOMWindowCrossFrame.postMessage':
_serialize_SSV,
On 2016/02/23 14:19:04, terry wrote:
> I'm wondering how the tests ran on integration w/o any problems.

Good question. Maybe there's some interaction with something else that happened
on master in between?

> 
> Do we need to add postMessage for ServieWorkerClient?

I don't see that class. But this covers everything in dart:html, except that it
turns out for _DOMWindowCrossFrame it's from template and I need to fix that
one.

> There are some other like CrossOriginServiceWorker (I guess that's
> _DOMWindowCrossFrame)?

CrossOriginServiceWorkerClient gets generated correctly without the special case
here.

> 
> What about postMessage in CompositeWorkerGlobalScope?

I think you mean Compositor...  That's in there, it's the second one in the
list.

> 
> Noticed we never did this for ServiceWorker in 39/45 there is a postMessage
> shouldn't that have been there too?
> 
> There is a postMessage in ServicePort for 45 should that be here too?
> 
> And what about Worker it was in 39 and there's still a postMessage in 45?

As above, everything in dart:html should be good now.
> 
>