Bug Tracker

Opened 13 years ago

Closed 13 years ago

Last modified 13 years ago

#912 closed bug (fixed)

Interface v1.1.1 - iSort problem with onChange

Reported by: spfjr@… Owned by: stefan
Priority: minor Milestone:
Component: interface Version:
Keywords: interface, sortable, onchange Cc:
Blocked by: Blocking:

Description

I was having a problem with the iSort class in Interface v1.1.1. Specifically, it appeared that the onChange method was not being called after the first change. I looked into it further and found that onChange would be called after all subsequent changes. However, the serialized list the method receives as an argument was always the list as it was before the change. I'm not that sure exactly how the code works but when I examined it, I found that it was determining if a change had been made before the change had actually been made to the DOM. I moved the code segment that commits the change up above the for loop that determines whether a change had been made. This fix seemed to work perfectly for me. However, I only tested it with the basic ordered list on my page, so I don't know if there are any unseen complications that may have arisen from the fix.

I saw one post on Nabble from a person who was having the same problem as me. I linked the changed files (both source and packed) in that post, which can be found here:

http://www.nabble.com/Interface-Sortable---onchange-not-firing-first-time-tf3138013.html#a8780169

I hope that does in fact solve the problem for everyone and not just me.

Shaun Fleming

Change History (1)

comment:1 Changed 13 years ago by stefan

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.