Hi,
On Thu, Apr 10, 2014 at 12:13 PM, Tobias Gierke < tobias.gie...@voipfuture.com> 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 :/ > > This does not sounds very clean: you will be updating all of thos for anything AJAX you do on the page. > 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() ... > In fact the setTimeout is "the way" of spanning a new thread on JavaScript: that part was added by Martin Grigorov, if I recall it correctly, precisely just to give wicket AJAX the possibility of complete processing. > > Thanks, > Tobias > > > > >> >> The page contains some dynamic images/icons that are included via >>> Image/DynamicImageResource (all have a 'antiCache' parameter in their URL >>> as well as a "last-modified" date that equals "now()" ). Both chrome and >>> firefox re-request these images after the download has completed and >>> looking at the network traffic/PCAP file I captured , I can see that >>> Wicket >>> is in fact delivering the PNGs to the browser. >>> >>> But: Chrome still renders these icons using the 'image is broken' >>> placeholder icon and Firefox/firebug shows the image downloads as 'never >>> completed' / 0 bytes downloaded (see attached screenshots). Firebug also >>> shows a pending GET request for a JavaScript file along with the image >>> download requests so the issue may be related to either caching or the >>> Wicket request processing in general. >>> >>> Any ideas ? >>> >>> Thanks in advance, >>> Tobias >>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>> For additional commands, e-mail: users-h...@wicket.apache.org >>> >>> >> >> > > -- > Tobias Gierke > Development > > VOIPFUTURE GmbH Wendenstraße 4 20097 Hamburg, Germany > Phone +49 40 688 900 111 Fax +49 40 688 900 199 > Email tobias.gie...@voipfuture.com Web http://www.voipfuture.com > CEO Jan Bastian > > Commercial Court AG Hamburg HRB 109896, VAT ID DE263738086 > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Regards - Ernesto Reinaldo Barreiro
