View Full Version : Ext.History fails when framed from a different origin

18 Jan 2011, 1:49 AM
Due to Ext.History trying to access `top.location.hash` it fails when the `top` document is from a different domain. This should not be the case.

Ext.History should use its current frame when working with the hash, alternatively doing a test when setting up if `top.location` is accessible.

18 Jan 2011, 4:07 AM
IMHO the target frame should be configurable and default to the current frame.

So you could still use the top frame by specifying:

frame: top