[
https://issues.apache.org/jira/browse/WICKET-1382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924354#action_12924354
]
Igor Vaynberg commented on WICKET-1382:
---------------------------------------
yeah, he is talking about target.add(imagecomponent)
in order to get images to get repainted in ajax one has to use NonCachingImage
so the ajax update also causes the url to be updated, otherwise browser wont
touch it.
i dont think it would be hard, in image.oncomponenttag() we can check if its
inside the ajax request and add the random nibble to the url
> Image could be made ajax aware..
> --------------------------------
>
> Key: WICKET-1382
> URL: https://issues.apache.org/jira/browse/WICKET-1382
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Reporter: Nino Martinez
> Priority: Minor
> Fix For: 1.5-M3
>
>
> It could be very cool if Image could be made ajax aware(so that it would add
> the random noise if it's added in ajax context).. Currently if you add a new
> image via ajax it's not updated(because the browser doesnt know it has to
> reload it). Normal procedure are to use noncaching image instead, but its
> confusing a lot of people.
> Pasted from mailinglist:
> most people want stable urls for their images i would imagine, so they
> can be cached by the browser.
> ...."
> in case of ajax this doesnt work because the url has to change so that
> browser needs to know to refresh it.
> maybe image can know if its requested within an ajax request and
> automatically add random noise to the url...there maybe room for
> improvement here.
> "......
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
