Philipp Hanes a écrit : > The code below works fine in Firefox (Windows), but in IE when I change > the state of one of the checkboxes, and then drag it past the other one, > it reverts to its initial state. > This only affects the one that's actively being dragged.
Obviously there is some issue with how IE implements the methods used by the drag code. But s.a.us does not seem to rely on HTML representations for this, which may have explained your checked status going to limbo. Maybe IE's cloneNode DOM method skips the checked property, but it is only used for ghosting, and your sample code doesn't enable ghosting, so that shouldn't be it also. Do you have a working demo online for this issue? > This might be a problem in prototype's serialization not handling the > distinction between"defaultChecked" and "checked" that's mentioned in > http://channel9.msdn.com/wiki/default.aspx/Channel9.InternetExplorerProgrammingBugs Actually, Prototype's behavior is correct in using the current state of the checkbox (the checked property) for serialization, since the *original* state (defaultChecked) is not what we're going after. The bug you mention highlights the necessity for the input to be in the DOM already before using the checked property, while the defaultChecked property is intended for initially setting the state. -- Christophe Porteneuve a.k.a. TDD "[They] did not know it was impossible, so they did it." --Mark Twain Email: [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
