I actually just solved it by putting the hidden_field inside another <td> instead of leaving it hanging outside. I have not checked in IE7. thanks for the heads-up! :)
2009/8/7 nirosh <[email protected]> > > hi > i faced the similar prob b4 1 month and then i find out this solution > cange > the function from onchange to onclick. this onchange not works with > IE7 > as well.ff works perfectly. > > nirosh > > On Aug 7, 9:35 am, Ram <[email protected]> wrote: > > i narrowed down the issue to one line of code in the item_row > > function. it tries to insert a value into a hidden_field which is kind > > of hanging inside <tr> tags. Here's the HTML and JS code.. > > > > HTML > > --------- > > <tr class="row"> > > <td>....</td> > > <td>....</td> > > <input class="item_id" id="order_item_id" name="order[item_id]" > > type="hidden" /> > > <td> > > <%= f.collection_select :item_name, > > Item.all, :item_for_order, :name, { :name => "select", :onchange => > > "item_row($(this));"} %> > > </td> > > </tr> > > > > JS > > ---- > > function item_row(element){ > > .... > > id = /* calculation excluded for brevity */ > > (element).up('.row').down('.item_id').value = id ; //this is the > > line that fails in safari but works in FF > > .... > > > > } > > > > Anything wrong with my HTML structure that Safari is rejecting? > > > > thanks. > > > > On Aug 6, 4:51 pm, Ram <[email protected]> wrote: > > > > > Hi all, > > > > > Im using the jNice plugin on a select box in a form of mine. Im also > > > calling a custom JS function which uses prototype on the same select > > > box. > > > > > <%= f.collection_select :item_name, Item.all, :item_for_order, :name, > > > { :name => "select", :onchange => "item_row($(this));"} %> > > > > > now both jNice and item_row() work in FF when i change the selected > > > value. But it does not work in Safari. In safari, the page jumps to > > > the top when i click on a selection, if i click on it again, jNice > > > works. item_row() does not. > > > > > Now im not sure what the problem is. Im using jQuery.noConflict to > > > avoid conflict between the two libraries and otherwise, the JS heavy > > > page is working fine. > > > > > Anyone with any experience/ tips on this one? > > > > > Vinay. > > > -- In Sport We Trust !!! --~--~---------~--~----~------------~-------~--~----~ 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 [email protected] 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 -~----------~----~----~----~------~----~------~--~---
