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

md-autocomplete triggering an ng-route change makes page unusable #7128

Closed
hweigel528 opened this issue Feb 11, 2016 · 2 comments
Closed

md-autocomplete triggering an ng-route change makes page unusable #7128

hweigel528 opened this issue Feb 11, 2016 · 2 comments
Assignees
@topherfangio
Labels
g3: reported The issue was reported by an internal or external product team. P1: urgent Urgent issues that should be addressed in the next minor or patch release.

Comments

@hweigel528
Copy link

I'm running into a few issues when using an autocomplete list which triggers a $location.path() call on an md-selected-item-change.

Fiddle: http://jsfiddle.net/999t17Lw/12/

note that when selecting B or C, the page gets successfully routed, but then nothing can be interacted with due to an md-scroll-mask. The hacky workaround of adding $mdUtil.enableScrolling() to the controller allows the page to be usable upon routing, but the autocomplete directive becomes useless on the new page.
@jelbourn jelbourn added g3: reported The issue was reported by an internal or external product team. P1: urgent Urgent issues that should be addressed in the next minor or patch release. labels Feb 11, 2016
@jelbourn
Copy link
Member

@robertmesserle This seems like something that could be handled by cleaning up the scrolling state on route change.

@cah-alexsukhodolsky
Copy link
Contributor

I'm able to easily reproduce this issue. I've put together a quick/easy fix.

cah-alexsukhodolsky added a commit to cah-alexsukhodolsky/material that referenced this issue Feb 25, 2016
@cah-alexsukhodolsky
fix(autocomplete): clean up md-scroll-mask element on destroy
da5a656 
* added test

Fixes angular#7049
Fixes angular#7128
@cah-alexsukhodolsky cah-alexsukhodolsky mentioned this issue Feb 25, 2016
Closed
ThomasBurleson pushed a commit that referenced this issue Feb 25, 2016
@cah-alexsukhodolsky @ThomasBurleson
fix(autocomplete): clean up md-scroll-mask element on destroy
acbd5c6 
* added test

Fixes #7049
Fixes #7128

  Closes #7291
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@topherfangio topherfangio

Labels
g3: reported The issue was reported by an internal or external product team. P1: urgent Urgent issues that should be addressed in the next minor or patch release.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@topherfangio @robertmesserle @jelbourn @hweigel528 @cah-alexsukhodolsky