Skip to content
This repository has been archived by the owner on Sep 5, 2024. It is now read-only.

md-autocomplete ng-click in md-not-found template with promise #5308

Closed
WedgeSama opened this issue Oct 22, 2015 · 13 comments
Closed

md-autocomplete ng-click in md-not-found template with promise #5308

WedgeSama opened this issue Oct 22, 2015 · 13 comments
Milestone
Deprecated

Comments

@WedgeSama
Copy link

If use of a promise to get items, the ng-click in the md-not-found template is not triggered. It can be reproduse with the HEAD doc example by check Simulate query for result?.

Do not work on the 1.0.0-rc1 too.

And the solution given in #5215 do not work in this case.
@epelc
Copy link
Contributor

epelc commented Oct 23, 2015

Why would you want the md-not-found template to show when you click on a button for one of the suggestions? It should just close the suggestions list all together and do whatever your ng-click handler wants.

@WedgeSama
Copy link
Author

It is not that. I want to click on a link in the md-not-found template but it did not trigger the ng-click event inside of the template (to create a new item based on the search terms for example).

@epelc
Copy link
Contributor

epelc commented Oct 23, 2015

Sorry for the misunderstanding. That makes perfect sense. This is definitely a bug.

Also it might have something to do with the pointer-events they tend to break things like this if they aren't set correctly. See https://developer.mozilla.org/en-US/docs/Web/CSS/pointer-events

@ThomasBurleson ThomasBurleson modified the milestone: 1.0-rc3 Nov 1, 2015
@luke14free
Copy link

+1

@robertmesserle robertmesserle modified the milestones: post-1.0 , 1.0-rc3 Nov 3, 2015
@lekev
Copy link

lekev commented Nov 7, 2015

+1

3 similar comments
@tiagopromob
Copy link

+1

@chunkai1312
Copy link

+1

@andrewmcconville
Copy link

+1

@RolandHeath
Copy link

This looks like a more complicated relative of #5526, so might be worth testing after #6103 is merged.

@mattdowell
Copy link

+1

1 similar comment
@steffi80
Copy link

steffi80 commented Jan 1, 2016

+1

@ThomasBurleson ThomasBurleson modified the milestones: post-1.0 , Backlog Jan 5, 2016
@egystr
Copy link

egystr commented Jan 11, 2016

+1

1 similar comment
@phsantiago
Copy link

+1

devversion added a commit to devversion/material that referenced this issue Jan 28, 2016
@devversion
fix(autocomplete): allow clicking on not-found template.
45dcdf6 
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
@devversion devversion mentioned this issue Jan 28, 2016
Closed
ThomasBurleson pushed a commit that referenced this issue Feb 1, 2016
@devversion @ThomasBurleson
fix(autocomplete): allow clicking on not-found template.
52a519e 
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 #5308. Fixes #6191. Fixes #5526. Closes #6103
ThomasBurleson pushed a commit that referenced this issue Feb 1, 2016
@devversion @ThomasBurleson
fix(autocomplete): allow clicking on not-found template.
4ef9674 
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 #5308 Fixes #6191 Fixes #5526

  Closes #6103
ErinCoughlan pushed a commit to ErinCoughlan/material that referenced this issue Feb 9, 2016
@devversion @ErinCoughlan
fix(autocomplete): allow clicking on not-found template.
3bb0e8a 
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
@ThomasBurleson ThomasBurleson modified the milestones: Backlog, Deprecated Apr 20, 2016
@ThomasBurleson ThomasBurleson modified the milestones: Deprecated, Backlog Apr 20, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
Deprecated
Development

No branches or pull requests