-
Notifications
You must be signed in to change notification settings - Fork 6.8k
feat(module:overlay): directive support disposeOnNavigation #18394
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please visit https://cla.developers.google.com/ to sign. Once you've signed (or fixed any issues), please reply here with What to do if you already signed the CLAIndividual signers
Corporate signers
ℹ️ Googlers: Go here for more info. |
@googlebot I signed it! |
CLAs look good, thanks! ℹ️ Googlers: Go here for more info. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure that this is necessary, because the directive dispose itself in ngOnDestroy
which should happen when the route changes as well.
@crisbeto Please check this bug of ng-zorro NG-ZORRO/ng-zorro-antd#1530 and this bug of components itself #11478. But I've not tested them with the latest release of CDK. |
I don't see where the overlay directive is being used in the linked example. |
@crisbeto Sorry for the misleading. Material seems just missing a property here. But in ng-zorro-antd we use Overlay in a declarative way. |
That was my point. Wouldn't that component that is used declaratively be destroyed when you navigate to a different route? |
I am afraid not, according to the reproductions provided in NG-ZORRO/ng-zorro-antd#1530. The user applied a router reuse strategy here so it seemed that the component is not destroyed? |
This was done in #27672. Closing. |
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. |
No description provided.