Make Dartium JS interop implementation more robust in the presence of JS paths that touch dart:html…

Make Dartium JS interop implementation more robust in the presence of JS paths that touch dart:html types. Note that the dart2js implementation was already robust in the presence of dart:html types.

BUG=
R=alanknight@google.com

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

[Jacob, 2015-11-04 04:21:30]

jacobr@google.com changed reviewers:
+ alanknight@google.com, terry@google.com

[Jacob, 2015-11-04 04:21:31]

See issue https://github.com/dart-lang/sdk/issues/24817

[Alan Knight, 2015-11-04 18:44:14]

lgtm

https://codereview.chromium.org/1415463019/diff/1/tests/html/js_typed_interop...
File tests/html/js_typed_interop_test.dart (right):

https://codereview.chromium.org/1415463019/diff/1/tests/html/js_typed_interop...
tests/html/js_typed_interop_test.dart:395: test('js path contains html types',
() {
nit: Not clear to me what this testing.

[Jacob, 2015-11-04 19:01:30]

https://codereview.chromium.org/1415463019/diff/1/tests/html/js_typed_interop...
File tests/html/js_typed_interop_test.dart (right):

https://codereview.chromium.org/1415463019/diff/1/tests/html/js_typed_interop...
tests/html/js_typed_interop_test.dart:395: test('js path contains html types',
() {
On 2015/11/04 18:44:14, Alan Knight wrote:
> nit: Not clear to me what this testing.
This case would fail previously 
note the path to propertyOnWindow intentionally bounces back between types that
were auto-proxied with the old dart:js JsObject class.

[Jacob, 2015-11-04 23:47:50]

Committed patchset #1 (id:1) manually as
6bfbb93d72af3c4b1ab882994d32647725e8691d (presubmit successful).