Drag from a grid demo give Javascript errors when in vertical mode

Our pure JavaScript Scheduler component
Post Reply
User avatar
bprescott_msd
Posts: 10
Joined: Sat Apr 20, 2019 11:08 pm

Drag from a grid demo give Javascript errors when in vertical mode

Post by bprescott_msd » Thu Oct 10, 2019 6:52 pm

We are using the latest version of the Scheduler control, and have run into an issue when our customers try to drag from a grid to the scheduler in vertical mode. The drag operation fails, and the developer tools console shows Javascript errors when you are dragging the item from the grid over the scheduler. Here is what the error looks like on our web site:

Code: Select all

Uncaught TypeError: Cannot read property '0' of undefined
    at VerticalEventMapper.resolveRowRecord (scheduler.module.js:94190)
    at Scheduler.resolveResourceRecord (scheduler.module.js:88584)
    at Drag.onTaskDrag (schedulerpage.js:246)
    at Drag.trigger (scheduler.module.js:5084)
    at Drag.update (scheduler.module.js:41944)
    at Drag.internalMove (scheduler.module.js:41883)
    at Drag.onMouseMove (scheduler.module.js:41899)
    at HTMLDocument.handler (scheduler.module.js:11606)
To see this same error in action, you can just go to the "Drag from a grid demo" example page on the Bryntum web site (https://www.bryntum.com/examples/scheduler/dragfromgrid/), edit the code, and toward the bottom and add this line into the new Scheduler area:

Code: Select all

mode: 'vertical',
Then once the scheduler changes to vertical mode, when you try to drag an item from the grid onto the scheduler, you will see the Javascript error in the dev tools console.

User avatar
mats
Core Developer
Core Developer
Posts: 14658
Joined: Sat Dec 19, 2009 11:41 pm
Location: Sweden
Contact:

Re: Drag from a grid demo give Javascript errors when in vertical mode

Post by mats » Thu Oct 10, 2019 7:06 pm

Tired of debugging javascript errors in web applications? Try our new error logging service RootCause, or read more on the Sencha blog

@bryntum
Facebook
API documentation

Post Reply