You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using your plugin to build some autocomplete fields in a form. I'm also using the Appendo plugin to dynamically add rows to my form. However, an autocomplete field, when duplicated, doesn't keep the autocomplete functionality. I'd need to manually re-apply the quickselect() method.
I think this can be fixed using the .live() -- and now .on() -- binders in jQuery. Any thought of an update?
Thanks!
The text was updated successfully, but these errors were encountered:
Can't you just add a callback on the appendo call to call .quickselect() on the new element? You can also pass params including the auto-selection data to into the quickselect function.
Daniel is no longer alive... but I worked with him a bit including that he developed quickselect for my use as well as his so we went back and forth on this project quite a bit.
I have written a similar script that I generally use myself now that may work better for you if you have issues with quickselect then checkout jselect: https://github.com/joshaven/jselect (If you need a feature added to JSelect then I would be much more likely to work on this project). quickselect was built on other code that I found complicated to manage so I did a re-write from scratch to accomplish the same thing and included testing to keep things from breaking.
I can leave this open but I don't have any plans at this point to add functionality to quickselect.
I'm using your plugin to build some autocomplete fields in a form. I'm also using the Appendo plugin to dynamically add rows to my form. However, an autocomplete field, when duplicated, doesn't keep the autocomplete functionality. I'd need to manually re-apply the quickselect() method.
I think this can be fixed using the .live() -- and now .on() -- binders in jQuery. Any thought of an update?
Thanks!
The text was updated successfully, but these errors were encountered: