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

Bug: md-autocomplete does not remove div.md-scroll-mask after losing focus. #3371

Closed
mbarakaja opened this issue Jun 19, 2015 · 31 comments
Closed

Comments

@mbarakaja
Copy link

md-autocomplete when focused, adds a div.md-scroll-mask element on top of other elements.

But randomly, it does not remove the mask element after losing the focus. Blocking any interaction with the other components under the mask, leaving the application unusable.

This happening to me in Google Chrome with the version 0.10.0 of Angular Material. I see this same bug in the Angular Material demo demo page.

@gustavoaalves
Copy link

I'm also with this same problem

@jgoux
Copy link

jgoux commented Jun 22, 2015

This is related to : #3287
This is a major bug because the entire app is unusable.

@mbarakaja
Copy link
Author

+1

@tolemac
Copy link

tolemac commented Jun 23, 2015

is it solved? why is closed?

@jgoux
Copy link

jgoux commented Jun 23, 2015

@tolemac I think it is closed because it's a duplicate of #3287

@tolemac
Copy link

tolemac commented Jun 23, 2015

oh! yes @jgoux, I thought you had closed your topic because of this, it's the opposite.
Sorry and thanks ;)

@cnjsstong
Copy link

+1

13 similar comments
@hitigon
Copy link

hitigon commented Jul 13, 2015

+1

@matheusamaral
Copy link

+1

@jmcpeak
Copy link

jmcpeak commented Sep 23, 2015

+1

@DaHaiz
Copy link

DaHaiz commented Sep 30, 2015

+1

@neonko
Copy link

neonko commented Oct 2, 2015

+1

@gsautr
Copy link

gsautr commented Nov 23, 2015

+1

@bastianwegge
Copy link

+1

@berkyl
Copy link

berkyl commented Nov 25, 2015

+1

@alexkb
Copy link

alexkb commented Nov 26, 2015

+1

@arne-s
Copy link

arne-s commented Dec 2, 2015

+1

@gbaj
Copy link
Contributor

gbaj commented Dec 18, 2015

+1

@alzalabany
Copy link

+1

@Ross-Rawlins
Copy link

+1

@qrpike
Copy link

qrpike commented Jun 1, 2016

+1

@mschering
Copy link

This has not been fixed in 1.10-rc5.

@devversion
Copy link
Member

@mschering This issue is closed. Please submit a new issue, if you're able to reproduce the issue in the latest version.

Please notice, that a Codepen is desired.

@nicolac18
Copy link

+1

3 similar comments
@RooTooZ
Copy link

RooTooZ commented Jul 18, 2016

+1

@ravzski
Copy link

ravzski commented Jul 28, 2016

+1

@rolintoucour
Copy link

+1

@mzaarour
Copy link

+1
Please solve it, the whole app is unusable

@TomSeldon
Copy link

Not sure why this issue has been closed, it's still very much a problem.

@devversion
Copy link
Member

@TomSeldon This issue is was closed because it seems to be fixed within 0.10.1 (#3287 (comment)).

I'm also not able to reproduce that issue anymore. Please submit a new issue by following the issue template. Including a proper demo.

@orenagiv
Copy link

Doesn't seem like this is resolved.
Continued here:
#3287 (comment)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests