This content has been marked as final. Show 2 replies
js debugging is one of my least favourite activities. To find out at what poing it is going wrong, my approach would be:
First, open an alert on the body onUnload event.
If that works, do a simple reload of the parent page.
If that works, I'm not sure.
Thanks for the idea.
In one of the many, many results I got back last night when I Googled "window.opener.location", there was a discussion about " ...location" returns an object not a string but that it will act like a string on most occasions. I think that "window.opener.location.replace(xxx)" really wants xxx to be a string version of the URL. This kind of flew right by me last night. So today I updated the onUnload to: <body onUnload="window.opener.location.replace(window.opener.location.toString());">. Like before, this works just find on my development system.
I've sent my customer service team this new version along with a test version that has an alert box in it; i.e., <body onLoad="alert(window.opener.location.toString()); onUnload="window.opener.location.replace(window.opener.location.toString());">.
If the new real change doesn't work for the customer, then they can put the test file in place and capture the result of the alert so I can see what's up with that. What the alert box should show is the exact URL string that is in the address bar of the page I'm trying to refresh with the ...Replace()) funciton.
Thanks again for your suggestion.