You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
matsbryntse opened this issue
Mar 6, 2023
· 1 comment
Assignees
Labels
bugSomething isn't workingforumIssues from forumlarge-accountReported by large customerOEMOEM customerpremiumresolvedFixed but not yet released (available in the nightly builds)
We've had an issue raised that our released scheduler component is spewing errors when the page is scrolled. After doing a bit of digging it looks like Locker service doesn't support the PointerEvent created in
onScheduleScroll.
We've seen this in bryntum gantt version 5.2.1, and want to be able to patch that release due to restrictions on changes in patches in Salesforce. So I would appreciate any support you can offer in working around this.
I've attached a screenshot of the exception we're seeing, can we avoid using PointerEvent in this scenario?
Thanks,
Gareth
The text was updated successfully, but these errors were encountered:
bugSomething isn't workingforumIssues from forumlarge-accountReported by large customerOEMOEM customerpremiumresolvedFixed but not yet released (available in the nightly builds)
Forum post
Hi folks,
We've had an issue raised that our released scheduler component is spewing errors when the page is scrolled. After doing a bit of digging it looks like Locker service doesn't support the PointerEvent created in
onScheduleScroll.
The documentation indicates that PointerEvent is not supported within LWC.
https://developer.salesforce.com/docs/component-library/tools/locker-service-viewer
We've seen this in bryntum gantt version 5.2.1, and want to be able to patch that release due to restrictions on changes in patches in Salesforce. So I would appreciate any support you can offer in working around this.
I've attached a screenshot of the exception we're seeing, can we avoid using PointerEvent in this scenario?
Thanks,
Gareth
The text was updated successfully, but these errors were encountered: