@devoncarew 

> It was a bit of an aha moment when I found out that they weren't compatible.

I'm pretty sure in javascript-land they _are_ compatible, so that is a slight ouch for us Dartisans :(   I assume if this ever becomes IDL generated they would be compatible?  I'm not sure why a `dart:html` FileReader rejects an `html.FileEntry` whose implementation class is outside of `dart:html` ->  but I am curious :)

> In an ideal world, the faithful mapping is auto-generated, and the high-level convenience layer is hand-coded.

Ok, that makes sense.  I am ok either way, but with all the confusion around proxies at the moment I think there are some benefits to giving the user a strongly typed object.

@financeCoding 

> would chrome.FileEntry entry = new chrome.FileEntry(file); for the Media Gallery PR?

I haven't used Media Galery, but I think we should be consistent across the entire API.  That is, either return `js.Proxy` everywhere or return `chrome.FileEntry` and `chrome.DirectoryEntry`. 

That pull request has been up for a while, is @DrMarcII  handling it?  I can take a closer look tomorrow if you like, but I don't have any experience yet with that API.

cheers,