Status: New
Owner: [email protected]
Labels: Type-Defect Priority-High Component-SES
New issue 1962 by [email protected]: untame({}) breaks for-in on Firefox
37, 38 beta
https://code.google.com/p/google-caja/issues/detail?id=1962
Firefox 37 and 38.0 beta.
var o = frame.untame(frame.iframe.contentWindow.eval('({})'));
for (var x in o) {}
The for loop throws "TypeError: undefined is not a function". This
shouldn't even be possible (without proxies, and there aren't any proxies
here), so it's probably a browser bug.
Any untame()d record object exhibits the problem. The unsafe eval is just
to have less machinery involved.
Other language meta-operations (e.g. getOwnPropertyNames) on the object
work normally.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
---
You received this message because you are subscribed to the Google Groups "Google Caja Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
