-
Notifications
You must be signed in to change notification settings - Fork 495
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Text annotations do not move with annotated target #4172
Comments
Moving to |
Customer has raised this https://jira.camunda.com/browse/SUPPORT-22608 also. |
Raised in another way as its confusing a customer - bpmn-io/bpmn-js#2215 (comment) |
Raised via bpmn-io/bpmn-js#2226, too. |
Related to #4492. |
This also happens when you move a pool |
It started happening in v16.4.0. Specifically with bpmn-io/bpmn-js@ca230c3 |
Probably worth to checkout bpmn-io/bpmn-js#2049 to understand the original intend (why we worked on bpmn-io/bpmn-js#2078 in the first place). The space tool, starting from [email protected] / [email protected] is local per default, which in combination causes this issue. |
After a discussion with @nikku, we concluded that text annotations should move when using a local space tool if they are inside of the participant, but NOT when they are outside (unlike external labels which always move with the target). A possible follow-up is to apply a similar behavior to groups. |
Describe the bug
Using the space tool I'm used to text annotations moving with the annotated target. Since a couple of releases this does no longer seem to be the case. In fact the annotations stay where they are, and if I use them extensively, then it takes a long time to put them back to their to be expected place:
Note how the behavior changes whether I#m within a participant making space or outside of it.
Steps to reproduce
Expected behavior
Text annotations move with elements, same as labels.
Environment
Additional context
Also raised in SUPPORT-22608
SUPPORT-25375
Depends on bpmn-io/bpmn-js#2226
The text was updated successfully, but these errors were encountered: