-
-
Notifications
You must be signed in to change notification settings - Fork 8.4k
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
When the number of unresolved async component caches exceeds max
set to KeepAlive, nothing is rendered
#11427
Labels
🔨 p3-minor-bug
Priority 3: this fixes a bug, but is an edge case that only affects very specific usage.
scope: keep-alive
Comments
Of course setting |
kakkokari-gtyih
changed the title
#10899 reappears when the number of unresolved async component caches exceeds
When the number of unresolved async component caches exceeds Jul 24, 2024
max
set to KeepAlivemax
set to KeepAlive, nothing is rendered
Just updated issue title for clarity |
5 tasks
Any updates on this? |
edison1105
added
scope: keep-alive
🔨 p3-minor-bug
Priority 3: this fixes a bug, but is an edge case that only affects very specific usage.
labels
Jul 30, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
🔨 p3-minor-bug
Priority 3: this fixes a bug, but is an edge case that only affects very specific usage.
scope: keep-alive
Vue version
v3.5.0-alpha.3, v3.4.34 (Vue SFC Playground)
Link to minimal reproduction
https://play.vuejs.org/#eNrNVN9P2zAQ/ldu2cOK1CYtsJcqVGoRD9vQhlbeCJpMcqWGxLZsJy1C/d93dpysnRhD2steIufuu+8+3w8/R3Ol4qbGaBqlJtdcWTBoazXLBK+U1BaeQeMKdrDSsoIPBP3Qu85lpebBESf+z3EdAhYHgEUAZCKXwrSIS06HM7jJBLSUw+60oNNtB81rrVE4JAkajI8cSZLAJIblhtt8DVaGhHe4khqDPI1Glg2aOBN0s2teoaztYHAEZzN4dokCb9ywskZin2RiN4TJeNynOO5T3LH8scszHwITBTzJGnImqGwIds0sfRBIsSVOA3IVZDASJKSFghtVsics3qxn7PWctnrSpO0S9Yd+LFZEZpH+ANKCN/5Ax5LdYTlLuVA1CXpSeJZFmhVcZhE0o0oWWJIlZCLb1Ccj05h+khnMIU1ajn8lnLSEiz3CQPluNIIlWqjY1pV0AqNRl+0LopqXvEGYkrdlCT7yLmujkIrXW8iWU5GlcOMx5YYCurm6CZJuiSBNelSvwgd3ZYT3K1aWrsd71ORfT2aXki4r7uM4ThP63QtODprQmn5TmCb9hdpOJW2rDmKjoRftN+iFbWQbxi0I3MAVrRM3OBiEyfaTszdKwTyEYzcyb56Z87BefY2mMP+bWL/N/4nYxWtiraGNXPH7+MFIQYL9otG8UjgvUX9TltMbk0XTdgWdjyZBbj57m9U1+jfJx6wxf3zB/mC2zpZFV3Qn1A1mUe+zTN8jrYVzXyy/4pbOvZOWpy4J/Yrzu6tS7TS2sEUtCpK9h/NqP/lXl8b02lxs6f0x3aWcUIfceXwWUddc+/509V9yT+JTH0dPEFXxR4PacVIBT+KP8XjESrVm8Um0+wkHmA1e
Steps to reproduce
(Reproduction was modified from #10899)
max
to1
inKeepAlive
(Set
max
to a number less than or equal to the number of unresolved asynchronous components)What is expected?
Expect CompA to be rendered correctly, or start loading again
What is actually happening?
CompA is not rendered when you back from CompB
System Info
Any additional comments?
Parent issue: misskey-dev/misskey#14170
The text was updated successfully, but these errors were encountered: