Fix for events fired on different isolates.

Fix for events fired on different isolates.

Ensures that a DOM callback will be fired on the isolate that it
originated on.

BUG=5151491
TEST=https://chromereviews.googleplex.com/3624031/

Committed: https://code.google.com/p/dart/source/detail?r=798

[Siggi Cherem (dart-lang), 2011-10-24 20:07:13]

lets also make native_IsolateNatives_bind a noop
(compiler/lib/implementation/isolate.js), and run the dartcombat tests
(client/samples/dartcombat) to see that nothing breaks there.

[vsm, 2011-10-25 18:44:46]

PTAL

Removing Isolate.bind exposed further issues.  Calling isolate$runEventLoop in
the dom layer feels like a hack.

[Siggi Cherem (dart-lang), 2011-10-26 19:45:38]

-floitschv8@gmail +floitsch@google

lgtm

I think you could also remove the 'bind' function from IsolateNatives in the vm
('runtime/lib/isolates.dart')

http://codereview.chromium.org/8370031/diff/4001/client/testing/unittest/unit...
File client/testing/unittest/unittestsuite.dart (right):

http://codereview.chromium.org/8370031/diff/4001/client/testing/unittest/unit...
client/testing/unittest/unittestsuite.dart:130: }, 0);
<< (fix indent)

[floitsch, 2011-10-27 11:56:04]

LGTM!