The set_number_of_grownups action does the job and then updates the
partial:
render :update do |page|
page['room_list'].replace_html :partial => "bookings/room_list"
end
The first time, everything works just fine. But subsequent changes of
the select fire the observer twice - at least to AJAX calls show up in
Firebug. (It happens with Safari, too.)
Maybe the old observer is still sitting around and gets a twin once the
partial is re-rendered. Strange though, no matter how often you change
that select, the number of fired AJAX calls is always 2. That's on Rails
2 with Prototype 1.6.
render :update do |page|
page['room_list'].replace_html :partial => "bookings/room_list"
end
The first time, everything works just fine. But subsequent changes of
the select fire the observer twice - at least to AJAX calls show up in
Firebug. (It happens with Safari, too.)
Maybe the old observer is still sitting around and gets a twin once the
partial is re-rendered. Strange though, no matter how often you change
that select, the number of fired AJAX calls is always 2. That's on Rails
2 with Prototype 1.6.
Yes, could be. And since there is no way to assign the prototype
observer to a js variable, you can't disable it before the call. Most
likely it's the old observer triggered by the replace and then replaced
itself, so they don't stack up infinitely, but get fired twice.
For you specific problem i don't see, why you want to re-render the
whole select tag, since it's options are constant anyway.
Worth a try may be splitting the partial and not reinstalling the
observer.
The hard way: Look at the generated code, take it as sample to write
your own observer, assigned to a variable name, so you can disable it
until the ajax response installs a new one.
If it's for select boxes only, you really don't need an observer. You
can get similar results by using remote_function together with the
onchange event.
observe_field is more interesting for text fields where you would have
to hook into the keyevents to get similar results.
If it's for select boxes only, you really don't need an observer. You
can get similar results by using remote_function together with the
onchange event.
observe_field is more interesting for text fields where you would have
to hook into the keyevents to get similar results.
Great, that's the solution - and works like a charm with almost no
changes at all.