Caja is using Proxy.create

[GoogleCodeExporter]

While debugging a Firefox crash (bugzil.la/1113980), I came across code that 
suggests that Caja is still using Proxy.create. We have plans to remove the old 
API in the future (bugzil.la/892903), so it would be good if Caja started using 
the new API. 

Does Caja work without Proxy.create? Do you have any idea how long replacing 
Proxy.create is going to take?

Thank you,
Tom

Original issue reported on code.google.com by evilp...@googlemail.com on 20 Dec 2014 at 3:19

[GoogleCodeExporter]

Thanks for reporting this. It does indeed need to be updated to the ES6 API.

Original comment by erights@google.com on 22 Dec 2014 at 5:15

• Changed state: Accepted

[GoogleCodeExporter]

There's a catch here, which is why we haven't done this already. ES5/3 emulates 
the Proxy.create API, and Domado depends on using proxies in both ES5 and ES5/3 
mode. Thus, we can't do this update until we're actually completely dropping 
support for ES5/3 (or we want to deal with more complicated backports). But 
that should be possible soon.

That said, I don't see any reason not to prepare the changes in anticipation.

Original comment by kpreid.switchb.org on 22 Dec 2014 at 5:21

• Added labels: Component-Domado, Component-SES
• Removed labels: Component-Other