Error closing the panel of an autocomplete inside a destroyed view. #7315
Assignees
Labels
P2
The issue is important to a large percentage of users, with a workaround
Comments
josephperrott
added
the
P2
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Sep 27, 2017
Fixes an error that was being thrown, because the autocomplete tries to run change detection on a destroyed view. Fixes angular#7315.
|
Hi @crisbeto , may i know whats the status of this issue? It has been quite some time. |
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Jan 10, 2018
Fixes an error that was being thrown, because the autocomplete tries to run change detection on a destroyed view. Fixes angular#7315.
jelbourn
pushed a commit
that referenced
this issue
Jan 24, 2018
Fixes an error that was being thrown, because the autocomplete tries to run change detection on a destroyed view. Fixes #7315.
jelbourn
pushed a commit
to jelbourn/components
that referenced
this issue
Jan 29, 2018
…7365) Fixes an error that was being thrown, because the autocomplete tries to run change detection on a destroyed view. Fixes angular#7315.
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Bug, feature request, or proposal:
Bug
What is the expected behavior?
Should not throw any error
What is the current behavior?
Error being thrown when attempting to close the panel of an autocomplete that is inside a destroyed view.
What are the steps to reproduce?
Plunker Link
Error Scenario
Step 1: Click on the button to open the view
Step 2 : Click on the AutoComplete but do not close the Panel
Step 3: Click on the button to close the view
Success Scenario
Step 1: Click on the button to open the view
Step 2 : Click on the AutoComplete
Step 2a : Close the Autocomplete Panel
Step 3: Click on the button to close the view
What is the use-case or motivation for changing an existing behavior?
Should not throw error
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Material Beta 11
Is there anything else we should know?
Related to (#5446) (880e6d5), #5413
The text was updated successfully, but these errors were encountered: