Skip to content

TASK: New 9.1 Drag and drop: Let server feedback determine node removal from the dom - #4103

Draft
mhsdesign wants to merge 1 commit into
neos:9.1from
mhsdesign:task/drag-and-drop-followup-4018-avoid-movedNode-remove
Draft

TASK: New 9.1 Drag and drop: Let server feedback determine node removal from the dom#4103
mhsdesign wants to merge 1 commit into
neos:9.1from
mhsdesign:task/drag-and-drop-followup-4018-avoid-movedNode-remove

Conversation

@mhsdesign

@mhsdesign mhsdesign commented Mar 25, 2026

Copy link
Copy Markdown
Member

With the 9.0 fix #4018 we can adjust Neos 9.1 where we currently get the inline drag and drop to function by removing the dom node manually. This is no longer necessary and saves us the todo to actually verify that the server can move the node

How to reproduce: Implement a command hook or ACL which the Neos Ui is unaware of.

What I did

How I did it

How to verify it

…al from the dom

With the 9.0 fix neos#4018 we can adjust Neos 9.1 where we currently get the inline drag and drop to function by removing the dom node manually. This is no longer necessary and saves us the todo to actually verify that the server can move the node
@Sebobo

Sebobo commented Mar 25, 2026

Copy link
Copy Markdown
Member

As I said in #4018 we have to verify that the feedback is handled fast enough in real environments, to prevent having the node twice for a while.

@Sebobo
Sebobo self-requested a review April 1, 2026 08:22
@mhsdesign
mhsdesign marked this pull request as draft April 15, 2026 19:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants