Skip to content
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

Activated hook is not triggering when mounting childs of an async component #7276

Open
dbssman opened this issue Dec 5, 2022 · 7 comments · May be fixed by #7286
Open

Activated hook is not triggering when mounting childs of an async component #7276

dbssman opened this issue Dec 5, 2022 · 7 comments · May be fixed by #7286
Labels
has PR A pull request has already been submitted to solve the issue 🐞 bug Something isn't working scope: keep-alive

Comments

@zhangzhonghe zhangzhonghe added 🐞 bug Something isn't working scope: keep-alive labels Dec 6, 2022
zhangzhonghe added a commit to zhangzhonghe/core that referenced this issue Dec 7, 2022
zhangzhonghe added a commit to zhangzhonghe/core that referenced this issue Feb 4, 2023
@yxchai
Copy link

yxchai commented Mar 6, 2023

@dbssman Is this resolved on your side? Is there a temp workaround for this? Thanks.

I noticed there's a PR waiting approval. Is there anyone can look into it? @zhangzhonghe Any luck with getting the PR reviewed and released? Thanks.

I'm experiencing the same thing. And I can recreated this bug in SFC Playground too.

In my playground, the first time you open it, the child component inside the async comp is mounted but never triggering the activated hook. That's the first time the async comp is loaded. But if you click on the toggle button, I can see the child component inside the async comp is triggering activated.

@zhangzhonghe
Copy link
Member

zhangzhonghe commented Mar 6, 2023

Any luck with getting the PR reviewed and released? Thanks.

@yxchai You could leave a comment in #7286 and @yyx990803 to review it. Maybe it will get yyx's attention.

@dbssman
Copy link
Author

dbssman commented Mar 22, 2023

@dbssman Is this resolved on your side? Is there a temp workaround for this? Thanks.

@yxchai I have a workaround but very specific to my project and that might not work for you, or not be what you need, If you're still interested in it lemme know.

@yxchai
Copy link

yxchai commented Mar 28, 2023

@yxchai I have a workaround but very specific to my project and that might not work for you, or not be what you need, If you're still interested in it lemme know.

Thanks for the reply, @dbssman, I was able to work out a way in my project specifically. So, all good here.

zhangzhonghe added a commit to zhangzhonghe/core that referenced this issue Apr 12, 2023
zhangzhonghe added a commit to zhangzhonghe/core that referenced this issue Apr 23, 2023
zhangzhonghe added a commit to zhangzhonghe/core that referenced this issue Apr 23, 2023
zhangzhonghe added a commit to zhangzhonghe/core that referenced this issue Apr 24, 2023
@719media
Copy link

This bug affected me unexpectedly today. I assume bandwidth just isn't there to get this reviewed and pushed. Just commenting to keep this thread alive!

@Justineo Justineo added the has PR A pull request has already been submitted to solve the issue label Jul 15, 2023
@ritilyn1991
Copy link

same problem in 3.5.8

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
has PR A pull request has already been submitted to solve the issue 🐞 bug Something isn't working scope: keep-alive
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants