I'm sorry I forgot to mention that I am using version 1.4.19 With a little reverse engineering I noticed that maybe one of the cases this happens is this: an ajax button is pressed, showIncrementally is executed, but the actual ajax request is postponed because its channel is busy. When the time comes to actually execute the request, the request is stopped because of precondition check, and thus hideIncrementally is never called. This loses the count. A fix might be to call hideIncrementally when the ajax request precondition is not met. As to why the precondition is not met, I am guessing it's because the previous ajax request did DOM replacement in a way that the precondition of the queued request is no longer met.
2011/11/18 Ernesto Reinaldo Barreiro <[email protected]>: > Martin, > > Before switching to 1.5.3 I was working with 1.5.x trunk and I think > it was the same there... but I can´t say that assertion is 100% true. > > As said in my case this happens to me on a modal window because my > indicator panel blocks the UI and that blocking div is behind the > modal. It should not be very difficult to produce a quick-start for > this issue (I guess). > > Best regards, > > Ernesto > > On Fri, Nov 18, 2011 at 12:02 PM, Martin Grigorov <[email protected]> > wrote: >> On Fri, Nov 18, 2011 at 12:59 PM, Ernesto Reinaldo Barreiro >> <[email protected]> wrote: >>> I have also noticed that with 1.5.3... I normally block the page with >>> div to prevent this but for links on a modal window it happens to me >>> (because blocking div is behind modal). >> >> And you didn't experience this with 1.5.2 ? >> Maybe https://issues.apache.org/jira/browse/WICKET-4071 is involved ? >> >>> >>> Regards, >>> >>> Ernesto >>> >>> On Fri, Nov 18, 2011 at 11:53 AM, Nazaret Kazarian >>> <[email protected]> wrote: >>>> Hi, >>>> >>>> I have added a global ajax indicator to all my pages by having all >>>> pages (through a TemplatePage superclass) implement the >>>> IAjaxIndicatorAware interface. >>>> >>>> Generally it works, but I have noticed that it is quite easy to get >>>> the ajax indicator stuck spinning indefinitely, by issuing many ajax >>>> calls quickly the one after the other. For example if I press an ajax >>>> button multiple times quickly the busy indicator gets stuck. >>>> It seems as if the Wicket.show(hide)Incrementally js functions lose >>>> count of ajax requests and the busy indicator is never actually >>>> hidden. >>>> >>>> Has anyone encountered this problem? >>>> >>>> Thanks a lot >>>> >>>> Naz >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >> >> >> >> -- >> Martin Grigorov >> jWeekend >> Training, Consulting, Development >> http://jWeekend.com >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
