It looks buggy to me to make outer window to keep mCrypto alive. It should be inner window. I wonder if one can even get a security exception on a web page if a page from domain A first accesses .crypto and then a new page from domain B is loaded and it accesses .crypto. B might not be able to access .crypto, at least if A set an expando property on it, so that the wrapper is preserved.
This was fixed at some point.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.