On Thu, Apr 10, 2014 at 1:13 PM, Tobias Gierke
<[email protected]
wrote:
Hi,
What do you exactly mean by the rendering of the page after download
completed? You repaint a part of the screen via AJAX? And this is
the one
giving problem with images?
Good point. I just investigated the AJAX response returned by the
server
when clicking the 'Start download' button on the modal dialog and I
noticed
that along with the JavaScript snippet that does the "setTimeout(...)"
there are also a lot of AJAX component updates that are obviously
generated
by components with overridden onEvent() methods. I didn't write the
code so
I wasn't aware of this :/
I suspect that the issue I'm seeing is caused by the Wicket AJAX
library
being interrupted by the "setTimeout()" call while processing the
component
updates... proving this will unfortunately take some time since the
page
has a lot of different components that all override onEvent() ...
JavaScript is single-threaded. There is no way to interrupt it.
By using setTimeout/setInterval functions you just add tasks to the
queue
that this single thread processes.
I stand corrected ;) But how come - given that setTimeout() just adds
a task to some "queue" - the actual magnitude of the timeout has an
effect ? My queues are usually processed first-to-last ;)
Forgive my ignorance, I just read
http://ejohn.org/blog/how-javascript-timers-work and was enlightened ;)
Cheers,
Tobias
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
