[
https://issues.apache.org/jira/browse/WICKET-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748136#action_12748136
]
Rodrigo De Castro commented on WICKET-2100:
-------------------------------------------
I upgraded to 1.4.0 and the same thing:
INFO: Initiating Ajax GET request on
../?wicket:interface=:3:tabpanel:panel:app_graph_panel:1:graph::IBehaviorListener:0:1&random=0.7774967316771
INFO: Invoking pre-call handler(s)...
INFO: Channel busy - postponing...
INFO: Channel busy - postponing...
INFO: Channel busy - postponing...
INFO: Channel busy - postponing...
INFO: Channel busy - postponing...
INFO: Channel busy - postponing...
INFO: Channel busy - postponing...
INFO: Channel busy - postponing...
INFO: Channel busy - postponing...
> DynamicImageResouce blocks loading of AjaxLazyLoadPanel
> -------------------------------------------------------
>
> Key: WICKET-2100
> URL: https://issues.apache.org/jira/browse/WICKET-2100
> Project: Wicket
> Issue Type: Bug
> Components: wicket, wicket-extensions
> Affects Versions: 1.3.5
> Reporter: Sergio Garcia
> Assignee: Matej Knopp
> Fix For: 1.3.6, 1.4-RC3
>
> Attachments: TestPage.html, TestPage.java, TestPanel.html,
> TestPanel.java
>
>
> The loading process of an image which loads its contents from a
> DynamicImageResource blocks changing of an AjazLazyLoadPanel from indicating
> image to content. "respond(...)" method of AbstractDefaultAjaxBehavior from
> AjaxLazyLoadPanel is never called.
> Within the attached quick start there is a forced delay because the image is
> too small and loads too quick to force the error. I think the problem is
> that loading the first dynamic resource changes state of the page from
> "domready" to "load" and attached AjaxLazyLoadPanel script ignores it's
> execution.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
