Workaround for 11854 (broken type check)

Workaround for 11854 (broken type check)

This works around the broken type check.

Alexandre: It also works if we use "JsFunction" instead of
"Serializable<JsFunction>" for the type check.  Is there a case where
we have the latter but not the former?

I also put in a status fix / fail for IE10.  That seems to be a
separate issue.

BUG=11849
R=alexandre.ardhuin@gmail.com

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

[alexandre.ardhuin, 2013-07-16 19:49:18]

> Is there a case where we have the latter but not the former? 

Callback class only implements Serializable<JsFunction>. The test "invoke Dart
callback from JS with this" will fail if you use "JsFunction" instead of "var"
in "factory JsObject(var constructor, [List arguments])".

[alexandre.ardhuin, 2013-07-16 19:51:32]

On 2013/07/16 19:49:18, alexandre.ardhuin wrote:
> > Is there a case where we have the latter but not the former? 
> 
> Callback class only implements Serializable<JsFunction>. The test "invoke Dart
> callback from JS with this" will fail if you use "JsFunction" instead of "var"
> in "factory JsObject(var constructor, [List arguments])".

There is the same kind of class structure in package:js between Proxy and
FunctionProxy.

[alexandre.ardhuin, 2013-07-16 19:52:12]

lgtm

[vsm, 2013-07-16 19:53:12]

On 2013/07/16 19:51:32, alexandre.ardhuin wrote:
> On 2013/07/16 19:49:18, alexandre.ardhuin wrote:
> > > Is there a case where we have the latter but not the former? 
> > 
> > Callback class only implements Serializable<JsFunction>. The test "invoke
Dart
> > callback from JS with this" will fail if you use "JsFunction" instead of
"var"
> > in "factory JsObject(var constructor, [List arguments])".
> 
> There is the same kind of class structure in package:js between Proxy and
> FunctionProxy.

I'm guessing we don't test that in checked mode with Dart2JS, so we haven't hit
this bug.

Are you okay with the current workaround (with 'var') until the blocking bug is
fixed?

[vsm, 2013-07-16 19:55:34]

Committed patchset #1 manually as r25065 (presubmit successful).