874787 - Support legacycaller on proxy bindings

Status: RESOLVED FIXED

(Core :: DOM: Core & HTML, defect)

Comment 1

[Boris Zbarsky [:bzbarsky]]

So what's needed here is:

1)  Passing ProxyIsCallable as the last argument to NewProxyObject in these cases.
2)  Setting up generation of call() and maybe construct() for the proxy handler for the
    interface; presumably the construct() could actually always throw and live on
    DOMJSProxyHandler.

and then it should all work.  Or something.

Comment 2

[Boris Zbarsky [:bzbarsky]]

Doing this now should be simpler, I think; we can just hang it off the JSClass directly.

But Chrome's usecounters claim this feature is not used (at least down to 0.01% of sites), so maybe we don't even need it.

Comment 3

[Boris Zbarsky [:bzbarsky]]

Looks like it's actually used on 0.03% of sites according to the Google folks, and bug 969030 comment 4 says we'll need this for web compat.

Comment 4

[Boris Zbarsky [:bzbarsky]]

Attachment: Add support for legacycaller on proxy bindings.

Comment 5

[Boris Zbarsky [:bzbarsky]]

https://hg.mozilla.org/integration/mozilla-inbound/rev/7aabad87c7d7

Comment 6

[Carsten Book [:Tomcat]]

https://hg.mozilla.org/mozilla-central/rev/7aabad87c7d7