-
-
Notifications
You must be signed in to change notification settings - Fork 8.9k
Closed
Labels
🔨 p3-minor-bugPriority 3: this fixes a bug, but is an edge case that only affects very specific usage.Priority 3: this fixes a bug, but is an edge case that only affects very specific usage.scope: keep-alive
Description
Vue version
v3.5.0-alpha.3, v3.4.34 (Vue SFC Playground)
Link to minimal reproduction
Steps to reproduce
(Reproduction was modified from #10899)
- Set
maxto1inKeepAlive
(Setmaxto a number less than or equal to the number of unresolved asynchronous components) - Switch to CompB before CompA resolves
- Switch back to CompA, and you can see that the contents of CompA are not displayed
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
System:
OS: Windows 11 10.0.22631
CPU: (12) x64 AMD Ryzen 5 3600 6-Core Processor
Memory: 4.31 GB / 15.95 GB
Binaries:
Node: 18.18.0 - C:\Program Files\nodejs\node.EXE
npm: 10.8.1 - C:\Program Files\nodejs\npm.CMD
pnpm: 9.2.0 - C:\Program Files\nodejs\pnpm.CMD
Browsers:
Chrome: 126.0.6478.182Any additional comments?
Parent issue: misskey-dev/misskey#14170
Metadata
Metadata
Assignees
Labels
🔨 p3-minor-bugPriority 3: this fixes a bug, but is an edge case that only affects very specific usage.Priority 3: this fixes a bug, but is an edge case that only affects very specific usage.scope: keep-alive