Problem/Motivation

Drag problem: after adding a style to a component, cannot drag in component slot

Any display, add 2 components with one slot each
Can drag one in other slot
Add style like background on frst component
Cannot drage 2nd component to first component (with backgrouund) slot

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

just_like_good_vibes created an issue. See original summary.

pdureau’s picture

pdureau’s picture

just_like_good_vibes’s picture

Some results on my investigation :

in dropzone.js, if i remove the once on .db-dropzone--root,
and force re-scan of all draggable elements, then the bug disappears..

when a style is applied, one or some dropzone elements need to be re-treated with Sortable,
but the once on db-dropzone--root is preventing this from occuring.

just_like_good_vibes’s picture

after some thinking, i suggest the usage of "once.remove" (on the element which recevied a once call in the dropzone behavior) when we have a style update.

just_like_good_vibes’s picture

maybe not, i am now iterating on that problem, i already find some working solutions, but i think there may be event better options inside dropzone.js code and react to changes like styles update or other changes.

pdureau’s picture

just_like_good_vibes’s picture

Assigned: just_like_good_vibes » pdureau
Status: Active » Needs review

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

pdureau’s picture

Assigned: pdureau » mogtofu33
Status: Needs review » Reviewed & tested by the community

it works on for me

mogtofu33’s picture

Assigned: mogtofu33 » Unassigned
Status: Reviewed & tested by the community » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.