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
You can use jQuery, hook onto $(document).scroll(). Whenever the scrollTop passes a certain threshold, make it smooth scroll down to the end point.
ReplyDelete$(document).scroll(function() {
if ($(document).scrollTop() > ####) {
smoothScrollTo(###);
}
});
Ok so I would use setTimout to check the scroll position every so often and then if the scroll position is right, scare the user or whatever you are planning:
ReplyDeletevar checkScroll = function() {
if(window.scrollY > 1000) {
setTimeout(checkScroll, 100);
}
else {
doSomeScaryStuff()
}
}
// need to call it manually the first time
checkScroll();
make sense?
Detect the current position of the top of the window using http://api.jquery.com/scrollTop/ and the window element, and use the same method combined with .animate() to smooth scroll down.
ReplyDeleteHope that helps!