On 1/18/07, David Huynh <[EMAIL PROTECTED]> wrote: > Hi Scott, > > That iframe is used to detect when the user presses the Back and Forward > buttons of the browser so that undo/redo can be supported. What kind of > problem is it causing you?
Probably not Scott's problem, but one I have encountered on my own in intrusive composition scenarios: when __history__.html is loaded into a frame from a site where it does not exist, and where the error page contains javascript code which breaks free of frames (such as if( window != top ) top.location = location;), this wreaks havoc, shutting down Exhibit and anything else along with it. It would be useful having the option of specifying somehoe that Exhibit first try to load the history page via SimileAjax, ensuring that it is the history page it expects, before loading it into the iframe. Or, doing away with loading an external file at all, if possible. -- / Johan Sundström, http://ecmanaut.blogspot.com/ _______________________________________________ General mailing list [email protected] http://simile.mit.edu/mailman/listinfo/general
