The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex
or just:
ReplyDeletevar isEmbed = window != window.parent;
You could use iframe's onload event:
ReplyDelete<html>
<head>
<script type="text/javascript">
function load()
{
alert("Iframe is loaded");
}
</script>
</head>
<iframe onload="load()" src="/page.html">
</iframe>
</html>
You can check if you are in an iframe using this snippet:
ReplyDeletevar isInIframe = (window.location != window.parent.location) ? true : false;
based on that you can continue with your javascript code.
Probably the simplest method:
ReplyDeleteif ( self !== top ) {
// you're in an iframe
}
So, you check if the current window is the topmost window...