Closed philippfromme closed 2 months ago
BREAKING CHANGE: context pad is not an overlay anymore; is positioned absolutely and does not scale
How is this a breaking change? What changes from the customization point of view?
Tests only fail on Linux with Firefox. There the position seems to be off. 🤔
@marstamm Could you try this out with Linux & Firefox to validate that the position for sequence flows actually works?
I can reproduce the test failure locally on a non-headless firefox. The test does not have any visuals to compare but I can't see any difference between chrome and firefox when using it in bpmn-js.
I can spend some time investigating why it calculates the position differently, or we can just accept that it works despite this and skip the test conditionally
Confirmed to work for the user on Linux & Firefox. ✅
I tried to improve the deprecation notice. Ready for review.
I tested this (visually) against bpmn-js and observed that the positioning is slightly different:
Is this intended or an issue with my setup?
I adjusted the position so the margin scales with the canvas zoom. So the context pad doesn't scale but the margin does just like with the original context pad. We're using the same approach with the other non-scaling non-overlay UI elements: https://github.com/camunda/improved-canvas/pull/61/files#diff-a6b19a26ee73a0b10318b24b4bfa2c36bfd0c32443f520a13af79ef3af2a0b8cR47
I will go ahead an merge this.
Canvas#getContainer()
ContextPad#getPad
is deprecated but will still return{ html }
for those who need it