Our pure JavaScript Scheduler component


Post by team-mysterio »

Hi,

I'm trying to debug an error occurred on a user session but I'm not able to reproduce it

When our user tried to drag & drop an event on the scheduler, this error was thrown:

Error: Incorrect type for Rectangle.width, got "-0.5" (expected a positive Number)
at Cs.assertNumber @ ../bryntum-DUHuJmbp.js:312:6333
at set width @ ../bryntum-DUHuJmbp.js:329:346471
at lt.adjust @ ../bryntum-DUHuJmbp.js:329:347467
at lt.deflate @ ../bryntum-DUHuJmbp.js:329:347615
at tl.getHandleRect @ ../bryntum-DUHuJmbp.js:570:13682
at tl.isOverEndHandle @ ../bryntum-DUHuJmbp.js:570:12911
at tl.initResizeContext @ ../bryntum-DUHuJmbp.js:570:2684
at tl.dragStart @ ../bryntum-DUHuJmbp.js:570:3912
at tl.startDrag @ ../bryntum-DUHuJmbp.js:338:9316
at $s.start @ ../bryntum-DUHuJmbp.js:338:5659

And just after, a lot of

TypeError: Cannot read properties of undefined (reading 'offset')
at tl.moveDrag @ ../bryntum-DUHuJmbp.js:570:8217
at tl.trackDrag @ ../bryntum-DUHuJmbp.js:338:9517
at $s.track @ ../bryntum-DUHuJmbp.js:338:6042
at $s.move @ ../bryntum-DUHuJmbp.js:338:5130
at tl.onDragPointerMove @ ../bryntum-DUHuJmbp.js:338:11735
at tl.onDragPointerMove @ ../bryntum-DUHuJmbp.js:570:1423
at HTMLBodyElement.p @ ../bryntum-DUHuJmbp.js:330:8328

While I'm not able to reproduce it, I'm not able to attach something in this request, but maybe you can still helps me

  • Is this possible that this error depends on the screen resolution of the user ?
  • Can it also be linked to a zoom (browser and/or operating system) ?
  • Do you have any other things in mind that could help us ?

Thanks


Post by marcio »

Hey team-mysterio,

Thanks for reaching out.

Unfortunately, with the error, there is not much insight that we can provide. It seems like something related to Drag operation, but without a reproducible test case, there isn't much that we can help with.

There could exist a few reasons that this error is being triggered, which could include the screen resolution, browser/OS-related issue, or a misconfiguration, but as you say that it happens only to a specific user, looks like a very specific test case which we'll need to know more details regarding OS, browsers, and code to have an idea of what's causing that.

Are you using the latest version of our components?

Best regards,
Márcio

How to ask for help? Please read our Support Policy


Post Reply