Component using List feature - Difficult to drag order

[samc]

So there is a bit of a bug with component lists.
Essentially I have a component that has a list with many items (e.g. 50+)

When you drag to reorder one of the items and drop it in a new spot. The item is put to the top of the list. Each item contains a text and image attribute. Maybe the list of items could have a more stable way of dragging to a desired point. If anyone else has had trouble please chime in.

[tristup]

Hi Sam,

Thanks for reaching out.
It seems that you are having the same problem described in the following thread.

Cannot drag or order elements in/within component div

Thank you. Now I’ve come a little further. I tested it on Brave browser with a blank wordpress installation with no Wordpress plugins installed. The issue stays the same. As you can see in the video, IN THE INSPECTOR I cannot drag or move elements into or within the component instance. IN THE PREVIEW AREA I can do it, but not in the inspector. It seems to be a bug. Kind regards, Hannes

This is an ongoing issue that has already been reported to our issue tracker, so this issue will be queued for fixing by our development team.

Thanks

[samc]

I’m talking about a different issue here is a screenshot.

You can test this quickly in Custom attributes. add multiple elements and label one drag it to somewhere on the list and it lands at the top. makes the reordering very annoying to work with.

One unrelated question can we ask about removing the word bummer from the default 404 page text.
“The page you are looking for is no longer here, or never existed in the first place (bummer). …”
in the UK it can be considered a bit rude and not ideal for client websites.

bummer

Thanks

[salilou]

Yes, I am also facing this problem.
When I want to rearrange the custom colors, the drag and drop element always jumps to the start or end.

[samc]

Yes that right anywhere that uses this same UI has the problem.

@tristup can you ask if there is fix for this?

Thanks

[christian]

Hey guys,

Thanks for reporting. There is currently no fix but I have reported this to our development team to be queued for investigation.