Forum Moderators: martinibuster
What's the consensus on this? Is it OK for an AS publisher to have frame breaking javascript on every page?
Also, what's the best code? (Or do they all do pretty-much the same thing?) Is there one way of doing it to particularly avoid?
Thanks, all!
Just keep in mind some people couldn't find their butt with both hands and a flashlight and take much of what you read with a grain of salt.
Try this...
<script LANGUAGE="JAVASCRIPT" type="text/javascript">
if (top!= self) top.location.href = location.href;
</SCRIPT>
<script language="JavaScript" type="text/javascript">
<!--Break out of frames
if (top.frames.length!=0)
top.location=self.document.location; //-->
</script>
<script language="JavaScript1.1" type="text/javascript"><!-- // hide from old browsers
if (parent.frames.length > 0) top.location.replace(document.location);
// Escape from any referring site's frame, but preserve one-click "Back". -->
</script>
I think Ann posted this in a thread sometime back... (thanks!)
Jim
The code I listed above allows the back button but the frame busting used on my competitors site doesn't - unless you click back 2 times REAL FAST ;)
My competitor also did double page impressions but that was because the frame busting code was on a timer - why in the heck would anyone bust a frame on a timer?
Never mind - just answered my own question. Don't know if it's deliberate or not but there's a frame at the top of the site that displays a CPM ad and the timer seems to go off just about right after the CPM ad is displayed before the rest of the page.
Looks like double impressions *might* be the intent!
Nasty.