|
hi,
maybe it's only sth I did wrong but when I
used global registering for Ajax events it was somehow
overwriting my onComplete tasks defined in Ajax.Updater..
And I needed both of them to trigger. I've got
some ajax actions with different behaviour onComplete but all of these
actions needed 'spinner/indicator' so I thought global registering would be
good..
Is it normal behaviour ?
greetings to all,
Andrzej
----- Original Message -----
Sent: Friday, April 07, 2006 11:22
AM
Subject: RE: [Rails-spinoffs] ajax
loading message
I
faced the same issue, but was never able to resolve it using
this.
Maybe it was because I was testing using localhost and the responses
were too fast..but dunno!
Then
I tried doing it using the following -
Ajax.Responders.register({
onCreate: function(request)
{
Element.show(loading);
},
onComplete: function(request) {
Element.hide(loading);
}
});
This
was my global spinner image. This always worked fine.
Maybe you would want to give it a shot.
Thank you,
Mandy.
_______________________________________________
Rails-spinoffs
mailing
list
Rails-spinoffs@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
|
_______________________________________________
Rails-spinoffs mailing list
Rails-spinoffs@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
