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
It sounds to me like you have some event firing on each key press on you input field.
ReplyDeleteThings you can do :
If Chrome's profiler doesn't fit your needs, try FireBug or IE9's profiler which is quite decent. In IE9 you can see how much CPU time was spent on each function call.
Temporarily remove the handlers from the fields, one by one, and observe any changes in the performance.
Let me know how it goes!
Webkit has a 'profile' option. Open the developer tools (ctrl+shift+i) and click on 'Profiles'. From there you can see a record button (the circle) at the bottom. Click it and use your page as you normally would. Click it again to stop and inspect your timelines for your function calls!
ReplyDeleteAlternatively you can benchmark functions individually using:
console.time( "Some label" );
console.timeEnd( "Some label" );
I use firebug for these purposes. It includes a profiler.
ReplyDelete