Hi,
I have no idea but something you can try is replacing
target.appendJavaScript("setTimeout(\"window.location.href='" + url + "'\",
100);");
with a bigger timeout... or maybe $(function() { window....}); so that
download is triggered once DOM is ready.
On Thu, Apr 10, 2014 at 11:02 AM, Tobias Gierke <
tobias.gie...@voipfuture.com> wrote:
> ...sorry, forgot that sending attachments to mailing-lists does not
> generally work...
>
> http://picpaste.com/firebug.png
> http://picpaste.com/chrome_after_download.png
>
>
> Hi,
>>
>> We're using Wicket 1.5.11 with the approach described in
>> https://cwiki.apache.org/confluence/display/WICKET/
>> AJAX+update+and+file+download+in+one+blow to trigger a file download
>> from within a modal dialog. This all works fine, our problem is with the
>> rendering of the page after the download is complete.
>>
>> 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
>
>
--
Regards - Ernesto Reinaldo Barreiro
