Premium support for our pure JavaScript UI components


Post by bdent »

Hello-

After upgrading to the 4.2.6 release (from 4.2.1), we are getting console errors coming from the syncEventContentPosition function of SchedulerPro.module.js. This issue appears to start with the 4.2.4 release as we've tried to narrow it down by sequentially going up from 4.2.1. In addition, the issue only happens when a row is expanded and we go outside of the viewable area threshold.

The only way we are able to get past the issue is if our scheduler instance doesn't have any non-working time ranges.

Screen Shot 2021-09-24 at 10.50.55 AM.png
Screen Shot 2021-09-24 at 10.50.55 AM.png (60.53 KiB) Viewed 2216 times

As a result of this error, the timeline breaks and becomes blank and no longer functions as expected.

-Bryan


Post by mats »

Can you reproduce this in our examples too? A simple boiled down test case would be great.


Post by johan.isaksson »

Hi,

After seeing this demoed I am trying to reproduce it on our bigdataset demo in Scheduler Pro. Are you using the ResourceTimeRanges feature or the ResourceNonWorkingTime feature? Any other features enabled? And is there some action being performed on scroll?

Best regards,
Johan Isaksson

Post by bdent »

Hi Johan-

We are using the resourceTimeRanges feature. What we have observed as conditions to reproduce this are as follows:

  • Must be in Day View
  • One row should be expanded
  • Must scroll horizontally and vertically to ensure that the expanded row is completely outside of the view and upon bringing it back into view, the error appears in the console for us.
  • At least one non-working day has to appear in the scheduler

Below are how the features are setup for us:

tree: true,
  eventEdit: false,
  cellEdit: false,
  cellTooltip: false,
  scheduleTooltip: false,
  headerMenu: false,
  timeAxisHeaderMenu: false,
  eventMenu: false,
  cellMenu: false,
  eventDragCreate: { disabled: true, showTooltip: false, lockLayout: true }, // To allow real-time toggling, we have to provide defaults
  columnLines: false,
  eventDrag: {
    disabled: true,
    constrainDragToResource: true,
    showTooltip: false,
  },
  stickyEvents: false,
  stickyCells: false,
  eventDragSelect: false,
  eventResize: {
    disabled: true,
    showExactResizePosition: true,
    showTooltip: false,
    validatorFn: (event) => {
      const dragStart = event.startDate;
      const dragEnd = event.endDate;

  if (
    isBefore(startOfDay(dragStart), startOfDay(dragEnd)) &&
    isAfter(startOfDay(dragEnd), startOfDay(dragStart))
  ) {
    return true;
  } else {
    return false;
  }
},
  },
  eventTooltip: false,
  resourceTimeRanges: { tabIndex: null },

The stickyEvents and stickyCells were originally not specified until our call the other day. As a result of specifying those settings, the error changed and was shown to come from the relinkElements function. Please let me know if you need anything else.

Thanks!
Bryan


Post by johan.isaksson »

Hi,

I finally managed to reproduce the issue. It requires using a custom eventRenderer too. Hope to have it fixed for 4.3.1: https://github.com/bryntum/support/issues/3579

Best regards,
Johan Isaksson

Post by bdent »

Johan- Thanks for the persistence and update on this one!


Post Reply