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
Here's a solution using CSS animations. They're not supported everywhere, but I can't think of any alternative.
ReplyDeleteThis hides your message by giving it a font-size of 0, which is reset to 100% after a delay of one second. Every half-second the JavaScript restarts the animation by switching to a dummy animation which keeps the element hidden. (Demo on jsfiddle)
HTML
<div id="noscript-message">
Please enable JavaScript to use this page.
</div>
<div>
Spiffy JavaScript app here!
</div>
CSS
#noscript-message {
-webkit-animation-duration: 1s;
-webkit-animation-name: delayedDisplay;
color: blue;
}
@-webkit-keyframes delayedDisplay {
0% { font-size: 0;}
99% { font-size: 0;}
100% { font-size: 100%; }
}
@-webkit-keyframes delayedDisplay_dummy {
0% { font-size: 0; }
100% { font-size: 0; }
}
JavaScript
var message = document.getElementById("noscript-message");
setInterval(function() {
message.style.webkitAnimationName = "delayedDisplay_dummy";
setTimeout(function() {
message.style.webkitAnimationName = "delayedDisplay";
}, 0);
}, 500);
You would need to duplicate all of the webkit prefixed properties with the other vendor prefixes; I've omitted them here for clarity.
As far as I know, this is not possible, not without refreshing the page, at least not using just HTML and Javascript. The behaviour you are describing is not in any standard, so different browsers may act differently once a user has selected to disable javascript.
ReplyDeleteThe normal mechanism as a developer would be use a <noscript> element. Most browsers will display this if the page was loaded and javascript was disabled. Some browsers may display it also if the page loaded and the user then disabled javascript.
When scripting is disabled, the contents of this element comes up once the page is refreshed.
You could have your <div> inside a <noscript> element, and then use CSS to animate its opacity:
ReplyDelete@-webkit-keyframes showme {
0% { opacity: 0; }
100% { opacity: 1; }
}
@-moz-keyframes showme {
0% { opacity: 0; }
100% { opacity: 1; }
}
@-ms-keyframes showme {
0% { opacity: 0; }
100% { opacity: 1; }
}
#box {
-webkit-animation: showme 5s;
-moz-animation: showme 5s;
-ms-animation: showme 5s;
}
...Of course, browser support would be an issue.