Cursor Not Reset after Showing Not Allowed

Describe the Bug

Cursor behavior changing while connecting tasks module using arrow option.

When 2 objects are close and trying to connected the flow using arrow icon available from object tool bar. After mouse release inside another object also, cursor icon not changed from not-allowed mode to default mode.End user felt that its not allowed to add text or do other activities. Its changing only after the arrow icon from object tool tip.

Please find the attachment video for more clarity. May 23 2019 12_52 PM.zip

Steps to Reproduce

Steps to reproduce the behavior: cf. video above

1. Start creating a connection between to close elements
2. Drag the connection to target in a very quick manner

Hint: This does not occur every time, but in certain situations

Expected Behavior

not-allowed cursor should be removed when the connection is allowed.

Environment

Please complete the following information:

• OS: [Windows 10]
• Camunda Modeler Version: [3.*]

Additional Context

• dragging.out -> connect.out is not fired in certain situations, so the connect-not-ok marker is not cleaned up properly from bpmn:Process element.

---

Related to SUPPORT-6128 Related to SUPPORT-6143

[pinussilvestrus]

I updated the issue description to fill the expectations.

[pinussilvestrus]

So, let’s conclude: As it’s not a regression, let’s postpone this for the moment.

It’s also very hard to create a test case for this since the problem seems to be caused by a missing fired dragging.out event when the cursor leaves the bpmn:Process elements, which results in a missing cleanup of the connect-not-ok marker.

@RamjiRamachandran we are still open for external contribution which fixes the situation in diagram-js (cf. it’s not correctly cleaning up, since dragging.out --> connect.out is not fired).