Premium support for our pure JavaScript UI components


Post by bdent »

We are encountering an inconsistent issue when using the scrollEventIntoView function.

cf64cb06-4af8-486f-a0a7-b5419d154f07.png
cf64cb06-4af8-486f-a0a7-b5419d154f07.png (18.26 KiB) Viewed 219 times

Upon further review, the event always has as resourceId associated with it and our UI prevents creating an event without assigning it to a resource. When reviewing the code associated with the scrollEventIntoView function, it's checking for a resource within the resources array of the event object and when it doesn't find one, it produces the warning that you see in the screenshot above and subsequently does not perform the scroll to behavior. As a workaround, we've put code in place to check event.resources for an object in the array and if it doesn't find one, we then check event.resource and put that object in event.resources or if event.resource is null, we check event.resourceId then get that resource from the resource store and populate it in event.resources. This appears to have provided more consistent results for us, but is not ideal.

What would cause an event that is always associated with a resource upon creation to not have that resource populated in the event.resources array? This error has been observed for new associations (first item within a row in the scheduler) as well as existing and both for events within the viewable area and not.

Any insight or help as to why this is happening would be appreciated.

Thanks,
Bryan


Post by mats »

Very hard to say without a test case or a way to reproduce it. Are you able to reproduce this in our standard examples too? That'd be very helpful if you could provide the steps required.


Post Reply