[ANGULAR] Bryntum date picker triggers a window scoped callback when onTransitionEnd is called

[belms]

Hi Team,

When we transition forward or backward through a date picker in Bryntum gantt, we see that the code looks for a callback function and executes it.

We have a window.callback defined for a different purpose which gets called whenever we move through the date picker, and throws an error.

Can this be fixed?

I see this behavior in the latest version of bryntum gantt as well (Please check the video for recreation). Since we are on a older version, is there a way we can override this?

[Animal]

No code attempts to execute window.callback

Can you stop the code in the debugger and examine the call stack and see what code is at the base and doing this? This seems like a scoping issue. Something is being called with no thisObj and so usage of this inside there is using the window instance.

[Animal]

I've reproduced it using the video. Will create a ticket when I have tracked its cause.

[Animal]

We'll get this fixed soon: https://github.com/bryntum/support/issues/9754

[belms]

Hi,

Attaching a screenshot with debugger at the exact place where this is getting called

we just have something like

export const columnsData = [
    { type: 'startdate', text: 'Start', editor: { autoExpand: true } },
    { type: 'enddate', text: 'Finish', editor: { autoExpand: true } },
];

which is then used in ganttConfig as

 columns: columnsData,

Not sure where to apply a different scope

[belms]

We'll get this fixed soon: https://github.com/bryntum/support/issues/9754

Thank you

[deepak.jayaram]

Hey Team,

We're currently on version 5.6.8 and can't upgrade to 6.0.0 for a couple of months. Is there a short-term code override we can apply to fix or patch this?

[mats]

Fix is already getting merged tomorrow, so you can use the nightly build on Monday (or wait for 6.0.5). Will that work for you?