Welcome to WebmasterWorld Guest from 18.104.22.168
Forum Moderators: open
top.location = document.location;
have I screwed up the code or will I see these problems because I'm using this?
<added> I'm using it in the head section </added>
I had a similar problem, especially when framed by Lycos's "Fast Forward" feature. The frame-escape would often leave "broken" html fragments on the page.
I fixed it by moving the frame buster to the bottom of the page. Since the page is already (usually) cached, it the reload isn't usually disuptive.
Here's the code I was using:
if (parent.frames.length > 0) top.location.replace(document.location); // Escape from frame, but retain one-click "Back". -->
I'd love to hear some better suggestions - I got it working and forgot about it, but it's rather inelegant.
What I meant was that moving my code to the bottom of the page where it will force a reload (but usually from the browser cache) was inelegant - I certainly meant no disrespect to your code. Moving the frame-buster fixed the problem I was seeing, but forced the entire page to be reloaded - so I considered it a "band-aid" fix.
Earnestly awaiting more opinions...