If calendar.stockholm.css is loaded before schedulerpro.stockholm.css then the Calendar component stops reacting to mouse events and event rendering is a bit broken (all-day events disappear altogether):
first_calendar_then_schedulerpro.gif (10.13 MiB) Viewed 1323 times
However, if the stylesheets are loaded the other way around then everything seems to be working fine:
first_schedulerpro_then_calendar.gif (9.68 MiB) Viewed 1323 times
Are there any obvious fixes/workarounds available to unblock our dev teams?
By the way, the Scheduler Pro style is also messing with the compact calendar view (date picker) to the left of the Calendar.
Note the change in the overall size (paddings around day numbers), the title background colour, and the selected day marker.
By the way, the Scheduler Pro style is also messing with the compact calendar view (date picker) to the left of the Calendar.
This is handled too.
If calendar.stockholm.css is loaded before schedulerpro.stockholm.css then the Calendar component stops reacting to mouse events
What do you mean by mouse events precisely? I can see it doesn't allow to create events by dragging the cells. I opened ticket for it here: https://github.com/bryntum/support/issues/2821
Thank you for the recording. I can surely see it is working, but I don't really know how, because in v4.1.2 CalendarDrag feature listens to the pointermove event on the document like this:
EventHelper.on({
element : document,
pointermove : ...
});
So when it receives pointer event from the document, it shouldn't be able to get the target, because of the Locker Service restrictions. That is what I saw locally.
I am curios as to what could be the cause? How do you create the calendar component? Is there some special markup or LWC features that you use?
Or maybe you override document variable for the bundle? We did similar thing to the undefined variable, to avoid expensive window.undefined call: