Leaving the ui-select element does not trigger a "blur" event

[jdmcnair]

The inner input element of the ui-select does generate a blur, but this should bubble up and trigger on the ui-select element itself so that it can be used in form validation, etc.

[surabhi-batra]

+1

[jossemarGT]

+1 I know is pain in the neck, but this workaround worked for me #432 (comment)

BTW if you need to use (like me) angular 1.2.x use $watch instead of $watchGroup.

[avrame]

+1

[jaxspades]

So also in #432, @dimirc added an is-close attribute to the 0.12.0 milestone. That would probably work fairly well for a blur idea. I'm excited to see it in action, personally. I'd rather not have to use a decorator.

[xavierfuentes]

Hi, is there any progress made on this issue? thanks :)

[MiguelMike]

None of the suggested workarounds seem to work with the latest version of Angular and ui-select.

http://plnkr.co/edit/7fSAKmj3pLeeTaid4pMH?p=preview

[shanmugam-siva]

Is there any progress made on this issue?

[itchyny]

I have the same problem :(

[jacobharasimo]

still a problem, any progress?

Still looks like an issue. Going to try ttonyh's workaround.

[joel1618]

My work around for now was to put a watch on the ng-model field that the ui-select is bound to. Then when the value changes I can handle it how I want.

$scope.$watchGroup(['item.Make', 'item.Model'], function (newValue, oldValue) {
if (newValue !== oldValue) {
//Do Something because either item.Make or item.Model has changed.
}
}
Or maybe an OnChange event can be harnessed?
Hope this helps someone out!

[jaxspades]

Depending on how your model is setup, that watcher can help, but it can add performance concerns. This really needs a blur event, not only to keep things performant, but also to work similarly to other input widgets out there today.

[mikaeledgren]

+1

[wesleycho]

PRs welcome.