I've been working on this for a year or so now. Seems it's a quirk of IE.
My objective is similar to EdGoiga's, passing a variable back to the calling script using opener.variableName. In my case, the variable is a pretty big object containing an array of objects - data points x, y, z and time.
In Chrome, FireFfox and Safari this works as per the book. After the child window closes, the variable and its value persist in the opener window's script.
In IE - including the current ver 9, as soon as the child window closes, the variable in the opener window disappears.
Various posts around the forums suggest that passing a simple variable works, but it doesn't.
I have got it working, but I don't really understand how, but it's mind-bogglingly slow.
In my solution, the child script populates the the opener's object. Then the child script calls a function in the opener which populates another object defined in the opener from data in the child object using looping and explicit assignment.
The child window stays open until the function completes (even if I put the window.close before the call to the parent function which I find odd)
My problem now is that this parent function runs really slowly - 30 seconds to process 3,000 data points on IE with the CPU at 100%: Chrome et al get through it in under 1 second. So it would appear that IE is struggling, perhaps with context switching, and not "really" setting up the openervariable in the same context as the opener code. Who knows??
So, I've spent the last couple of days attempting to improve the performance but to no avail.
Most attempts fail with the error message that is the subject of this thread!
So, anyone with some creative thoughts would be welcome here.
> To post to this group, send email to prototype-scriptaculous@googlegroups.com.
> To unsubscribe from this group, send email to prototype-scriptaculous+unsub...@googlegroups.com.