Looking into it in detail, these two libraries have a different problem with the same consequence: UI.Next doesn't detect their events. Fortunately both are fixable with a little bit of code which I posted here.

  • Awesomplete doesn't trigger the change event at all, instead it uses a custom jQuery event awesomplete-selectcomplete. We can just listen to that event and trigger change ourselves.

  • Select2 triggers the change event as a jQuery event, whereas UI.Next listens to the DOM event. Again we can trigger the DOM event from a jQuery listener, with a bit of extra trickery to avoid infinite recursion (since the DOM event in turn triggers a new jQuery change event).
By on 1/14/2017 4:16 AM ()

Thanks for the excellent example solution! I would never have figured that out by myself.

By on 1/14/2017 12:53 PM ()
IntelliFactory Offices Copyright (c) 2011-2012 IntelliFactory. All rights reserved.
Home | Products | Consulting | Trainings | Blogs | Jobs | Contact Us | Terms of Use | Privacy Policy | Cookie Policy
Built with WebSharper