>From what I can see, the most likely cause of this is that there is an
issue with the dom, such that when you do the update, the browser is
not seeing the fields or ids correctly

A couple of suggstions:

Use firebug to carefully inspect the dom before and after the  updates
and make sure the ids are ok and that the elements are structured
correctly.

If you cannot see anything obvious, strip the view code down so that
the only things being rendered are the actual select fields.  Then you
should be able to see why the onchange is not firing.

If you get it down to  very simple/minimal  example that still
demonstrates a problem, post it here and i will see if i can repeat
it.

Tonypm
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to