Site freezes after selection and clearing on Autocomplete demo

[bradlygreen]

To reproduce on Chrome 43:

1. Go to https://material.angularjs.org/latest/#/demo/material.components.autocomplete
2. Select a state
3. Click the 'X' to clear the state
4. Try to click on anything else on the page. Observe the unresponsive status.

[ThomasBurleson]

@bradlygreen - Rob and I are are seeing something similar for Select menus... working on a fix today; seems to be present only with Angular 1.4.x.

[ThomasBurleson]

Occassionally the transitionEnd event will not fire and the '$mdUtil. waitTransitionEnd()' process will timeout; which rejects the pending promise. Using '.finally()' [consistently] allows the correct handlers to fire and will continuing to propagate the rejected promise.

[linkedrank]

Hello - is there progress on this? I am also experiencing this issue.

[topherfangio]

@linkedrank Per the close comment above, this was fixed in d6a938e. Are you still seeing this if you use the latest master code?

[linkedrank]

Apologies - somehow I missed the fact that it was closed.

I am still seeing it. I'm using the autocomplete in combination with a
grid. See this screencast: http://screencast.com/t/fItdc55Ae4VI.

One thing I am doing though is the below to hide the autocomplete on the
blur of the underlying input element. It's not ng-blur, so I end up having
to call $scope.apply, which could be I'm sure introducing something funny.
This blur event goes on to hide the autocomplete widget. However, this blur
tactic was working fine for the past week, and I've only now started seeing
this behavior. I updated to do AngularJS 1.4.5 yesterday, so I'm not sure
if that's the cause.

    if (scope.hideOnBlur) {
      setTimeout(function() {

document.getElementById(scope.autocompleteId).addEventListener('blur',
scope.onblur);
}, 0);
}

On Thu, Sep 3, 2015 at 6:07 PM, Topher Fangio notifications@github.com
wrote:

@linkedrank https://github.com/linkedrank Per the close comment above,
this was fixed in d6a938e
d6a938e.
Are you still seeing this is you use the latest master code?

—
Reply to this email directly or view it on GitHub
#3800 (comment).