Conflict resolution popup: Odd behavior on Cancel

[vladip]

Hi there,

Found an odd behavior in the Conflict resolution popup. It doesn't seem it's constant because I can't reproduce it in your Conflicts demo https://bryntum.com/products/gantt/examples/conflicts/.

• When you click on cancel the first time, the popup closes and opens again so you have to cancel 2x.

• If you then try to make and adjustment that violates the same constraint and the conflict resolution popup opens again and you click on cancel again then your changes are not reverted (cell stays in edit mode).

Here is a video on how to reproduce the issue in your Advanced demo https://www.loom.com/share/5394dce1364843f5b9558d9437663adf?sid=41cbd798-bda6-467a-9d83-f4967c7f9d1f.

[marcio]

Hey vladip

Thanks for reaching out and for the video on how to reproduce the behavior.

I created a ticket to fix that https://github.com/bryntum/support/issues/8514

[vladip]

Hi marcio,

Here is another issue, probably related to the previous one. Every new popup has the previous stacked messages. See the video:
https://www.loom.com/share/89ac927aa55b446cb514714418d46594?sid=ceec0ef8-6108-4551-b770-782206db8197

[ghulam.ghous]

Hi Vladip,

Thanks for reporting it. I have created a ticket here to fix it asap https://github.com/bryntum/support/issues/8676.

Regards,
Ghous

[nickolay]

@vladip Hi, the 2nd issue you reported has been resolved, the fix will be available in the next release and in the tomorrow nightly.

I'll be checking the 1st issue now.

[vladip]

Hi @nickolay, thanks for the quick fix.

I'm not sure if this is related to one of the previous issues, but I sometimes notice this strange behavior while conflicting (see the error in the console):

13b13a68e3704067a7f3dac9409530b4.mp4

(1.44 MiB) Downloaded 35 times

It looks like that's data-dependent because I see this error sporadically and can't figure out the common signs. Perhaps you could give me some insight into what might be affecting this?

[nickolay]

The exception says - some asynchronous calculation was attempted to be performed in the synchronous context. This is usually a bug, to tell more I need to be able to reproduce this, please provide a test case if possible.