Try a workaround for initMessageEvent bug.

Try a workaround for initMessageEvent bug.


BUG= http://code.google.com/p/nativeclient/issues/detail?id=2394
TEST=cd native_client; ./scons --mode=opt-host,nacl chrome_browser_tests

Note: For some reason, trybot runs aren't appearing here. You can see them at:
http://build.chromium.org/p/tryserver.chromium/waterfall?committer=dmichael@chromium.org

The constructor is the 'new right way' to do it anyway:
http://www.whatwg.org/specs/web-apps/current-work/multipage/comms.html

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=107591

[dmichael (off chromium), 2011-10-27 15:30:23]

I can find another reviewer if you're busy, but not too many people are in the
office yet that could look at this, and it's easy ;-)

[viettrungluu, 2011-10-27 17:11:00]

I'm told that the constructor is the new way to do things and should be
equivalent to the initMessageEvent (which is now deprecated), so this should be
okay. LGTM.

Someone should get to the bottom of why initMessageEvent is failing though.

[commit-bot: I haz the power, 2011-10-27 17:13:07]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/dmichael@chromium.org/8340019/1