Make WordPress Core

Opened 4 months ago

Last modified 4 months ago

#63817 new defect (bug)

Gutenberg List View – Drag & Drop Blocks Misbehaving with Nested Columns

Reported by: rahultank's profile rahultank Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version: 6.8.2
Component: Editor Keywords: reporter-feedback close
Focuses: ui Cc:

Description

When using the block editor’s List View, dragging a block from one nested column to another often results in the block being dropped outside the intended container. This disrupts the block hierarchy and can break the layout, forcing the user to manually move the block back into place.

Steps to Reproduce:

1.Create a new page in the Gutenberg editor.
2.Add a Columns block with three columns.
3.Inside the third column, add another Columns block (nested).
4.Add any block (e.g., Paragraph) inside the nested columns.
5.Open List View.
6.Try dragging a block from one nested column to another.

Expected Result:
The block should always be placed inside the target column.

Actual Result:
The block is often placed outside the intended nested column, sometimes even outside the main Columns block entirely.

Environment:
WordPress version: 6.8.2
Gutenberg version: bundled in core
Theme: Twenty Twenty-Five
Browser: Chrome 126 (Windows/macOS)

Attachments (1)

Screen Recording 2025-08-12 at 16.43.58.mov (1.1 MB) - added by callumbw95 4 months ago.
Video of my testing following the steps mentioned

Download all attachments as: .zip

Change History (3)

#1 @callumbw95
4 months ago

  • Keywords dev-feedback added

Hi @rahultank,

I have just taken a look into this, and I was unable to replicate this issue? Are you able to supply any further information about your environment?

Reproduction Report

Description

❌ This report validates whether the issue can be reproduced.

Environment

  • WordPress: 6.8.2
  • PHP: 8.4.7
  • Server: nginx/1.27.5
  • Database: mysqli (Server: 8.0.40 / Client: mysqlnd 8.4.7)
  • Browser: Chrome 137.0.0.0
  • OS: macOS
  • Theme: Twenty Seventeen 3.9
  • MU Plugins: None activated
  • Plugins:
    • Test Reports 1.2.0

Actual Results

  1. ❌ Error condition did not occur.

@callumbw95
4 months ago

Video of my testing following the steps mentioned

#2 @SirLouen
4 months ago

  • Keywords reporter-feedback close added; needs-patch dev-feedback removed
Note: See TracTickets for help on using tickets.