I solved it by calling a function on Sortable.onChange that renames my arrayName[n] fields according to their current position in the DOM. Seemed to be a simple and degradable solution.
On Mar 18, 11:44 pm, Tom Gregory <[EMAIL PROTECTED]> wrote: > Sam, > > You may want to look at Sortable.serialize and SortableObserver. > These would obviate the need for hidden input fields to determine > order.http://wiki.script.aculo.us/scriptaculous/show/Sortable.serialize > > Take a look in dragdrop.js to see how the Sortable Observer is used. > > TAG > > On Mar 17, 2007, at 10:25 AM, James Mitchell wrote: > > > > > On a post,browsers are not supposed to honor any specific ordering of > > inputs on the page. If you find one that does, great, but you can't > > assume that this will work on them all. > > > You'll need to manage ordering with input values instead of visual > > ordering. Instead of manipulating the order, try manipulating a set > > of corresponding hidden inputs that hold the order number. > > > -- > > James Mitchell > > The Ruby Roundup > >http://www.rubyroundup.com/ > > > On Mar 17, 2007, at 7:41 AM, sam wrote: > > >> Hello all, > > >> I'm having the following problem with Safari: I have input > >> type="hidden" fields inside li-elements whose order I edit using drag > >> and drop. When submitting the form, Safari submits the list in the > >> original order as listed in the page source, not the dynamically > >> created new order. The whole thing works as expected in Firefox. Does > >> anyone know how to resolve this problem? > > >> Thank you! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" 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-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
