[webkit-dev] Throwing SECURITY_ERR on cross-origin window.location property accesses

[Darin Adler]

On Aug 25, 2010, at 6:06 PM, Rob Barreca wrote:

> We need a way to test for the security exception or at least detect some other property of window.top and then do window.open(url) instead when that security error is trapped or we detect different-origin.

Does checking the value of window.top.location.href afterward work? Or maybe that doesn’t happen until some unpredictable amount of time later when the load makes progress?

    -- Darin