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

<Suspense> changes the order of elements when using v-for with a given key and a wrapper component #14173

Open
Labels
🔨 p3-minor-bugPriority 3: this fixes a bug, but is an edge case that only affects very specific usage.has workaroundA workaround has been found to avoid the problemscope: suspense
@koelnconcert

Description

@koelnconcert

Vue version

3.5.25

Link to minimal reproduction

https://play.vuejs.org/#eNq9VdtuGjEQ/ZWpXyASLHceCIlEc6mo1BBRpDzUUbWFgTjZ9bq2l4sQ/97xshhISitVSvMQ7cwZz5kZzzFr1lMqmKfIOqxrxlooCwZtqi65FLFKtIU1aJzCBqY6iaFAoQUPXSWxyv1BxRku0zH8oEOlUB9F5b48mMtxIo0FYTE2cOHYit+4BFiLSQdqJZBhjB0o1Gq1wqbkgboH6vX6IdDwQKPRKGy4fDxzJFxSXyMRY5LaYvEMLi5h7c5ktME8jFIk8oyY/rJMTZ+p2WzmFDus5bFWq/UKa3us3W67CgAeudyUoF6tVqmYbmU7aZoxGcSvotAiWQDdiZiDsasILzibCEPIqgPTCJfnMAsVtV1Vy3POsmAKN6lRSJ3l9jaBN8j8UC7Dw3Bw9wkGw+ubIfRuR/T/y+C6f9u/6o36gzsojhOtcWxhIewTTQc6L7giejeZQEw4O4Ny+TDn4b3Oy9NE58Eg5HacnL3JAR33mXvIrOwrruxLpskcN3TUTkb8r4w7wj3d7qtbObgCVmLW0EJOxSx4NokkXWRrwtmYyEWEeqCsoIXlrLNdIIeFUZQsPmc+q1PMt4HOPOH45Tf+Z7N0Ps7uNRrUc+TMYzbUM7Rb+ObrHS7p24NxMkkjiv4DOESTRKmrcRv2MZUTKvsgLqu2n2lUyNnI3CwtjXzXlCvURW53mjNSqZv7qdb35TaCZnaOVp2m6M70zEqOT7wuE5wKifc6Uabohejz2pUi/Qx+PNNe5nVr/JlqgaQvXyExZdoOF6GwIHEBlC8WBos01iSak6IvHeFO9rm3BLXq2d91mC/Mep2tlFP0JtPyqb3ZPYDv2uw71HzwHJ/+FfDXefSS+wvO3vH/0+W+krcCf93e9zlqt9jUVyNoBfUW2/wCEF1CyA==

Steps to reproduce

  • Render an array of elements using a component with async setup
  • Render new elements

What is expected?

Vue should render the elements in the same order as in the array.

What is actually happening?

Vue renders new elements in reverse order.

System Info

Any additional comments?

This is similar to#13559, but uses an additional wrapper element between the v-for-element and the async component.

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.has workaroundA workaround has been found to avoid the problemscope: suspense

    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