[Dropdown] Unable to attach handler to onChange or onAdd after a dropdown has been initialized

[douglasg14b]

If a dropdown has been initialized, you cannot add a handler for the onChange or onAdd events, it only works if they are added during initialization.

During init:

$('#testThings2').dropdown({ onAdd: function(addedValue){ console.log(addedValue); } });

After Init:

$('#testThings').dropdown('setting', 'onAdd', function(addedValue){console.log(addedValue)});

JSFiddle: https://jsfiddle.net/q7yg99Ld/

[fakenickels]

any updates on this?

[shadoWalker89]

This feature is a must have

[jlukic]

As a sidenote, this is specifically related to calling .setting() on the original <select> element, if you use setting('onAdd') on the generated dropdown everything works correctly.

[fakenickels]

@jlukic is right! It doesn't work on the select element, you invoke it in the element where the dropdown was initialized.

[shadoWalker89]

@jlukic But i will have to do something like this each time

$('#SomeSelect').closest('.ui.dropdown').dropdown('setting', 'onAdd', function(){});

What is expected is this

$('#SomeSelect').dropdown('setting', 'onAdd', function(){});

Maybe you could add this and deprecate the .ui.dropdown solution.

[jlukic]

module.setup.reference(), which is used to match a select to dropdown when invoking methods, was not correctly pulling the original dropdown instance when modifying the reference. It was using a new instance.

In current versions calling dropdown methods on a <select> worked for methods like set selected etc that dont change the instance data (since dom references are all still there), but setting does change the underlying data so it failed to work

[douglasg14b]

@jlukic Happy to see you back and committing :)

Anything the community can do to help? Based on the direction you want the project to go...etc?