Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings
/corePublic

updating keepalive include will cause asyn loaded components to not be cached. #14210

Open
Labels
🔨 p3-minor-bugPriority 3: this fixes a bug, but is an edge case that only affects very specific usage.scope: keep-alive
@huangxiuqi

Description

@huangxiuqi

Vue version

3.5.25

Link to minimal reproduction

https://play.vuejs.org/#eNrNVE2P0zAQ/SujXNJqS0MFp6hdsaA9LEiAlr1hpA3JtPHWcSLbSbuq+t8Z2/miKrBCCO0hUux58+Z5/DyH4Kqq5k2NQRwsdap4ZUCjqatLJnlRlcrAAfIZKFzPQOeJEOXu1v5nuOYSr/SjTN+VBJQoDRxhrcoCQuILmWQyLaU2kFIcVmczJgcmAUSZZKhimExhdQm+7CScRxZmtYVTJo/0DXSLv+ZbnCGslaJcGyXa4ZCTc4gP+EggascQ3SJWieAN3shU1Bm28a+hUxp+I2AH1Ttu0ryt5OU5xVEEdznXsONCUHJRNgj3Lv3et9TkCGmS5mjRpwXnTSJqW7YvaVH242uY/Cy+w65W4MDh1CuA8SF7wnziCOkEJ4gRk+dZ0IUDGQCFxj8zPoHQ89E9MbmMvDPJk7QwWFQiMUgrgKXtxQvXDIi5b8eKBacdYoFDE95Se7PGXBNyJIEFEHnSaGD1G99rY0oJb1LB0y1lDfdIzH7hfOmYl5GHU+oyGqkNZoHR5IM138wfdCnpyblGkQhK5QLVp8pw8gkL4q6FLHBufO/2jKpx1u2TF9Ltmf0Hvbd7LPisUKNq6Ox9zCRqg8aHr798xD3998GizGpB6N8Eb1GXorYaPextLTOSPcI5tTfuxXG5udPXe4NSd4eyQt21OjwL6CnaHv7q6IPcV/PXnR2oi91cGGbWeFrR2zsZRLh3IRoYSS0IYqlkUmDcOs2pcVOPnmTn3XbW1NKgal/0y9a2iqBKdkiLdSi/JI1P8W3Gm9aSbjx2hWgGHA796ujIzvivBVxckP3I9QoTjSPbWQv7AqcG7EfgP+rd4hk0b/Gfunf8AUnkbnU=

Steps to reproduce

In the example, there are two asynchronous components, withcomp1 included in theinclude list.
Click to switch components, switch tocomp1, then click "increase" to increment the counter, and then click to switch components twice more. You will find that the counter forcomp1 resets to zero.

What is expected?

After switching components, the counter in comp1 should retain its previous value.

What is actually happening?

After switching components, the counter in comp1 is reset to 0.

System Info

System:    OS: Windows 11 10.0.26100    CPU: (8) x64 Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz    Memory: 2.30 GB / 15.88 GB  Binaries:    Node: 22.18.0 - C:\Program Files\nodejs\node.EXE    npm: 10.9.3 - C:\Program Files\nodejs\npm.CMD  Browsers:    Chrome: 143.0.7499.41    Edge: Chromium (140.0.3485.54)

Any additional comments?

I've found the problem and the solution; can I submit a pull request?

Metadata

Metadata

Assignees

No one assigned

    Labels

    🔨 p3-minor-bugPriority 3: this fixes a bug, but is an edge case that only affects very specific usage.scope: keep-alive

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions


      [8]ページ先頭

      ©2009-2025 Movatter.jp