[
https://issues.apache.org/jira/browse/WICKET-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706805#action_12706805
]
Pedro Santos commented on WICKET-2262:
--------------------------------------
Sending the javascript generated code that is causing the problem:
wicketShow('testd--ajax-indicator');
var wcall = wicketSubmitFormById(
'formFilter22',
'?wicket:interface=:1:form1:test:lookupWindow:content:formFilter:tfFilter::IActivePageBehaviorListener:0:-1&wicket:ignoreIfNotActive=true',
null, function() {
;
wicketHide('testd--ajax-indicator');
}.bind(this), function() {
;
wicketHide('testd--ajax-indicator');
}.bind(this), function() {
if (window.event != null && window.event.keyCode == 13)
{
return Wicket.$$(this) &&
Wicket.$$('formFilter22');
} else {
return false;
}
}.bind(this));;
the snippet lines 12-16 was returned by preconditionScript method
> The starting of the ajax indicator don't respect AbstractDefaultAjaxBehavior
> preconditionScript
> -----------------------------------------------------------------------------------------------
>
> Key: WICKET-2262
> URL: https://issues.apache.org/jira/browse/WICKET-2262
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.6
> Reporter: Pedro Santos
> Priority: Minor
>
> I have add an AbstractDefaultAjaxBehavior to an component that implements the
> IAjaxIndicatorAware. My expectations was that the indicator start during the
> ajax requests. But it start an stay indicating an ajax processing that is not
> happening due an condition implemented on my extended
> AbstractDefaultAjaxBehavior preconditionScript that return false on the
> occasion.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
