Problem/Motivation

We are using this theme in our project with core 9.5.10 and facing the issue with tabledrag on layout builder sidebar.
dsdws

Steps to reproduce

Steps to reproduce

  1. Install Drupal 9.5.x-dev
  2. Install stable contrib theme
  3. Enable Layout builder and Layout builder modules
  4. Enable Layout builder on the article content type
  5. Go to Manage display
  6. Select a block and click 'Move'
  7. See that the drag-and-drop icon is not visible and you are unable to move the items

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Issue fork stable-3374736

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

nitesh624 created an issue. See original summary.

nitesh624’s picture

Issue summary: View changes
StatusFileSize
new9.58 KB
shyam_bhatt’s picture

Status: Active » Needs review
StatusFileSize
new1.99 KB
new67.32 KB

@nitesh624 I have checked this issue with the steps provided in the description. Please check the below patch to fix the issue for the stable theme only.

After patch:
2023-09-22/3374736-3-after.png

dishakatariya’s picture

Assigned: Unassigned » dishakatariya
dishakatariya’s picture

Assigned: dishakatariya » Unassigned
Status: Needs review » Reviewed & tested by the community
StatusFileSize
new197.13 KB
new95.26 KB

Hi, I have verified this issue on the Drupal 9.5.11 version and Stable contrib Theme set as by default. And the Tabledrag is not broken in layout builder sidebar.
Followed the below steps:
1. Install Drupal 9.5.x-dev
2. Install stable contrib theme
3. Enable Layout builder and Layout builder modules
4. Enable Layout builder on the article content type
5. Go to Manage display
6. Select a block and click 'Move'
7. See that the drag-and-drop icon is not visible and you are unable to move the items
Attaching the screenshots before and after patch.
Moving to RTBC,
Thanks.

kmonty made their first commit to this issue’s fork.

kmonty’s picture

The patch didn't apply against 2.1.0, so I opened an issue fork that is compatible. I'm not convinced about this patch's approach, but people who have a better understanding of Stable should know better.