-
Notifications
You must be signed in to change notification settings - Fork 3.4k
bug(autocomplete): ng-click doesn't work inside md-not-found #5526
Comments
+1 I'm running into this as well with version 0.11.4.
My controller function never gets called. As @stewones mentions, even the demo one doesn't work - it doesn't show the alert. |
+1 has been working in RC-1 and maybe RC-2, not working in RC-3 |
+1 not working since RC1 for me. |
as workout: self.$mdAutocompleteCtrl.mouseUp = function(){ its not good, but for those who need make it to work at any cost! |
My current fix is the following:
|
@dominicgoulet @nestorneto Eagerly waiting for a fix. |
Just override the mouseUp funcion of $mdAutocompleteCtrl. This worked for me. In my case I have a custom directive that uses the autocomplete component. So its easer for me to do that. |
@nestorneto How did you go about hiding the list? I tried it in a few different ways, but only dominicgoulet's hack worked. |
+1 |
What's your problem with the current workaround @vlopez5 ? |
@dominicgoulet I tried to do like your demo and still not possible click inside md-not-found. I am using RC5 |
Currently the Not Found Template will be removed for a few seconds from the DOM, that's why clicks not getting registered. This can be fixed by checking for the mouse position. The Mouse should be on the list. Fixes angular#5526
Finally, there is a fix for that issue. #6103 |
Thank you @devversion ! |
Currently the Not Found Template will be removed for a few seconds from the DOM, that's why clicks not getting registered. This can be fixed by checking for the mouse position. The Mouse should be on the list. Fixes angular#5526
Currently the Not Found Template will be removed for a few seconds from the DOM, that's why clicks not getting registered. This can be fixed by checking for the mouse position. The Mouse should be on the list. Fixes angular#5526
Currently the Not Found Template will be removed for a few seconds from the DOM, that's why clicks not getting registered. This can be fixed by checking for the mouse position. The Mouse should be on the list. Fixes angular#5526
Another workaround that worked for me is to change ng-click with ng-mousedown |
Currently the Not Found Template will be removed for a few seconds from the DOM, that's why clicks not getting registered. This can be fixed by checking for the mouse position. The Mouse should be on the list. Fixes angular#5526
Currently the Not Found Template will be removed for a few seconds from the DOM, that's why clicks not getting registered. This can be fixed by checking for the mouse position. The Mouse should be on the list. References angular#5308 Fixes angular#6191 Fixes angular#5526
Currently the Not Found Template will be removed for a few seconds from the DOM, that's why clicks not getting registered. This can be fixed by checking for the mouse position. The Mouse should be on the list. References angular#5308. Fixes angular#6191. Fixes angular#5526. Closes angular#6103
Thank You |
The text was updated successfully, but these errors were encountered: