that might work.

-igor

On Fri, Nov 18, 2011 at 1:45 PM, Nazaret Kazarian
<[email protected]> wrote:
> Yep, I will create a quickstart and create a jira.
>
> If it turns out to be a bug, until it gets solved, I am thinking of
> showing / hiding the busy indicator using js pre/post call handlers.
> And maybe also use the following code as a condition in post call
> handler to hide the indicator:
>
>        wicketAjaxBusy: function() {
>            for (var c in Wicket.channelManager.channels) {
>                if (Wicket.channelManager.channels[c].busy) {
>                    return true;
>                }
>            }
>            return false;
>        }
>
> Do you think that's a good idea?
>
>
> 2011/11/18 Igor Vaynberg <[email protected]>:
>> quickstart, jira?
>>
>> -igor
>>
>> On Fri, Nov 18, 2011 at 1:20 PM, Nazaret Kazarian
>> <[email protected]> wrote:
>>> That sounds reasonable. According to the scenario I described above,
>>> the indicator will always get stuck if you use channel type Drop and
>>> issue an ajax request on a busy channel.
>>>
>>>
>>>
>>> 2011/11/18 coincoinfou <[email protected]>:
>>>> Same problem with IndicatingAjaxLink when I switch to AjaxChannel.Type.DROP
>>>>
>>>> --
>>>> View this message in context: 
>>>> http://apache-wicket.1842946.n4.nabble.com/Ajax-busy-indicator-getting-stuck-tp4082837p4083026.html
>>>> Sent from the Users forum mailing list archive at Nabble.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]
>>
>>
>
> ---------------------------------------------------------------------
> 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]

Reply via email to