There is a disabled-in-ES5 test case which uses
imports.tameNodeAsForeign___. This test, and *an older version of* the
Google API taming Ihab is currently working on, are the only users of
imports.tameNodeAsForeign___.

The problem is that in ES5 mode, there is no
guest-code-shall-not-access-___ rule to hide behind, so making it
available under that name is not an option. However, using
frame.domicile.tameNodeAsForeign would be fine, provided the client is
in a position to obtain the domicile object.

Is there ever a case where this would be a problem? Do we have any
other existing users of tameNodeAsForeign___?

Reply via email to