Page 1 of 2

[VUE] Unexpected context menu behaviour

Posted: Mon Apr 12, 2021 5:55 pm
by foursite

Unexpected context menu behaviour when more then one type of componenet is on same page ,

If i have gantt or grid or scheduler with any combinations i.e gantt+grid or grid+scheduler or gantt+grid+scheduler i am seeing context menu dont dissapear after you click anywhere , sometime context menu of scheduler appears inside gantt or grid too

i have even tried to use scoped css but that dont work either as it seems dynamically inserted bryntum componenet dont have scopeid in there elements
I cant figure out the issue so plz guide me

here is the screenshare https://www.loom.com/share/17d0f8a81ed24fd3b72792d38c9cad11
here is the test project created with vue cli and bryntum examples from V4.1.0


Re: [VUE] Unexpected context menu behaviour

Posted: Mon Apr 12, 2021 6:49 pm
by mats

Can you please try this using latest 4.1.0 release? Still reproducible?


Re: [VUE] Unexpected context menu behaviour

Posted: Tue Apr 13, 2021 6:17 am
by foursite

this is usin 4.0.1 already


Re: [VUE] Unexpected context menu behaviour

Posted: Tue Apr 13, 2021 7:50 am
by mats

4.0.1 or 4.1.0?


Re: [VUE] Unexpected context menu behaviour

Posted: Tue Apr 13, 2021 8:26 am
by foursite

sorry i meant 4.1.0

"@bryntum/grid-vue": "4.1.0",
"@bryntum/gantt-vue": "4.1.0",
"@bryntum/schedulerpro-vue": "4.1.0",

Re: [VUE] Unexpected context menu behaviour

Posted: Tue Apr 13, 2021 10:51 am
by saki

It seems to be a bug; I have created the ticket: https://github.com/bryntum/support/issues/2654


Re: [VUE] Unexpected context menu behaviour

Posted: Wed Sep 08, 2021 1:11 pm
by foursite

i was wondering is this issue has been fixed?


Re: [VUE] Unexpected context menu behaviour

Posted: Wed Sep 08, 2021 4:29 pm
by mats

Yes I believe this was fixed a while back, please re-test using latest?


Re: [VUE] Unexpected context menu behaviour

Posted: Mon Sep 20, 2021 11:07 am
by foursite

Re: [VUE] Unexpected context menu behaviour

Posted: Mon Sep 20, 2021 11:28 am
by foursite

just updated packages to 4.2.6 and tried again with same test files and same issue is still there