In the generated Chrome Packaged App the variable is initialized:

var appWindow = js.context.chrome.app.window.current() as AppWindow;

The value of 'js.context' is a Proxy instance wrapping a JS object. I was going to suggest rewriting the generated code to include specific types, but even that won't work here. About half the methods documented for AppWindow are not even defined in the Dart class.

I'm not sure what to do about Proxy in general.

cc @devoncarew.
Set owner to @bwilkerson.

Attachment:
screenshot.png (93.99 KB)

Adding justin, who's thinking about how to improve this from the js interop library point of view.

cc @justinfagnani.

var appWindow = js.context.chrome.app.window.current() as AppWindow;

You definitely don't want to do this. appWindow is a Proxy, not an AppWindow. AppWindow lives in the dart:chrome library, which is a totally separate way of accessing the chrome apis. This example is using js interop.

I think we want to allow exactly that in the future. DOM objects that are sent via js-interop should be seamlessly "serialized" (by reference) instead of using proxies.

In any case, currently there's no real way to type Proxy objects, that's a future goal.

Removed this from the Later milestone.
Added Oldschool-Milestone-Later label.

Removed Oldschool-Milestone-Later label.

Closing as stale.