"on-remove" callback doesn't work with single select and "allow-clear".

[antch]

It appears that currently the onRemove callback is only executed when a multiselect option is removed. It makes sense that it should also be called when the user clears a single select when allow-clear="true".

[bradgreens]

👍

[damjtoh]

+1

[martynchamberlin]

+1

[wesleycho]

Can you post a Plunker reproducing this?

Commenters: Please avoid using +1, and use GitHub reactions - +1s only serve to pollute issues, preventing people from finding the important information needed to craft a fix/analyze a problem.

[martynchamberlin]

Sorry. GitHub Reactions came out literally a couple days after my comment, and long before the other +1s. But we'll definitely remember to use those going forward!

[antch]

http://plnkr.co/edit/ah66gkgU5TxTKnXFw9NF?p=preview

[edwin177]

For now, it looks like on-select is called with $item = null.

[jigar-dhulla]

@edwin177 on-select looks fine to me. issue is with on-remove as of now. http://plnkr.co/edit/Y8RskftrBB659cyG7M7K?p=preview

[edwin177]

Yup, I ran into the same issue and found this thread. I was just sharing my work-around until it's fixed. When you click clear, on-select is called with $item = null.

[antch]

Actually, on-select is called with undefined, not null.

[iberodev]

any progress on this?