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
{{ message }}
This repository was archived by the owner on May 29, 2019. It is now read-only.
Repository navigation
This repository was archived by the owner on May 29, 2019. It is now read-only.
Typeahead is-open change via document click does not trigger digest on original scope #5467
When typeahead's drop-down is open, clicking outside of it closes the drop-down but variable bound to is-open does not change to false. Here's a minimal test case.
Changing 'scope.$digest()' to 'originalScope.$digest()' here seems to fix the problem.
@azizmaredia20, hi there. Please understand that we are all unpaid volunteers on this team, managing a VERY popular OSS project. It maybe as simple as making the change indicated above, but we would need to make sure it doesn't have any negative side effects. I've flagged it as needing investigation and we will get to it. You will need to be patient.
Barring that, you could always fork the repo and make the change yourself using a custom build until this issue is fixed.
Activity
icfantv commentedon Feb 12, 2016
This looks like a good catch. @wesleycho, thoughts?
mkozhukharenko commentedon Feb 17, 2016
I've encountered the same problem +1
mkozhukharenko commentedon Feb 17, 2016
Found temporary workaround:
<input type="text" click-outside="typeaheadIsOpen = false;" ng-model="model" uib-typeahead="option as option.name for option in new.options | filter:{$:$viewValue}" typeahead-is-open="typeaheadIsOpen">I used click-outside directive to manipulate typeaheadIsOpen variable;
azizmaredia20 commentedon Feb 19, 2016
Hi mkozhukharenko,
can you please share your click-outside="typeaheadIsOpen = false;" directive code
azizmaredia20 commentedon Feb 19, 2016
Does anyone has a fix for this isssue?
icfantv commentedon Feb 19, 2016
@azizmaredia20, hi there. Please understand that we are all unpaid volunteers on this team, managing a VERY popular OSS project. It maybe as simple as making the change indicated above, but we would need to make sure it doesn't have any negative side effects. I've flagged it as needing investigation and we will get to it. You will need to be patient.
Barring that, you could always fork the repo and make the change yourself using a custom build until this issue is fixed.
azizmaredia20 commentedon Feb 20, 2016
@icfantv, Yes sure i will fork the repo and try to solve the issue
mkozhukharenko commentedon Feb 20, 2016
@azizmaredia20 I'm using IamAdamJowett/angular-click-outside directive
wesleycho commentedon Mar 5, 2016
Similar to the recently fixed issue with 313ba83, we should change this to
originalScope.fix(typeahead): change to original scope