Anyone found that sometime between 1.6.4 and 1.7.1 beta releases of Scriptaculous that something has changed with the way that the onChange is fired? In 1.6.4 it fired once, now in 1.7.1 beta it fires everytime you move the mouse. --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
nevermind, the line in dragdrop.js that causes it is fixed now ;) (maybe thomas fuchs will fix it sometime) On May 25, 11:07 am, JeDi58 <jed...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Anyone found that sometime between 1.6.4 and 1.7.1 beta releases of > Scriptaculous that something has changed with the way that the > onChange is fired? > > In 1.6.4 it fired once, now in 1.7.1 beta it fires everytime you move > the mouse.--~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
robert.j.mead-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
2007-May-25 13:22 UTC
Re: Sortable onChange fires for every mouse movement
I''ve pinned down where this seems to be happening ... The function _findRootElement in a sortable was added sometime between 1.6.4 and 1.7.1. This is now used in place of element = $(element); in the options declaration as element = Sortable._findRootElement($(element)); Setting this back to what it used to be seems to stop onChange firing on mouse move for nested sortables. Rob. On May 25, 1:47 pm, JeDi58 <jed...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> nevermind, the line in dragdrop.js that causes it is fixed now ;) > (maybe thomas fuchs will fix it sometime) > > On May 25, 11:07 am, JeDi58 <jed...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > Anyone found that sometime between 1.6.4 and 1.7.1 beta releases of > > Scriptaculous that something has changed with the way that the > > onChange is fired? > > > In 1.6.4 it fired once, now in 1.7.1 beta it fires everytime you move > > the mouse.--~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---