Telerik,

As per your article here - https://docs.telerik.com/kendo-ui/controls/scheduling/scheduler/how-to/scrolling/scroll-views-horizontally

If you do this, then enable selectable: true - it doesnt work correctly, essentially it only selects ever X group - hard to explain, please watch the video.

Is there a fix for this?

You can see the issue in the attached video (ZIPPED) and here is a modified dojo from yours with just selectable set.

https://dojo.telerik.com/@daniel_j/arUVUMAY

Thank You.

Hello Mark,

Thank you for reaching out. I tested the reported behavior using the provided dojo and it is working fine on my end. I am able to select slots in consecutive days and create events. Attached is a screencast of one of my attempts to reproduce the issue. did I miss any crucial step while trying to reproduce it? Are there any specific requirements for the reproduction of the behavior?

Regards,
Aleksandar
Progress Telerik

Aleksandar,

I cant wach that as it is a shockwave object - I dont have a player for that.

After a little more testing it is caused by high res monitors using Windows display scaling (my 2 4k laptops)

Does your monitor have a high res with scaling?

I turned windows scaling off - and it works fine. So its 100% the result of scaling.

Most laptops now have high res scaling so this is still an issue that we need a resolution for.

Thanks.

Aleksandar,

After even more testing the results change completely dependant on the width of the Scheduler - so it seems tied to the width of the slots.

As you will see in the attached video - each time I change the size of the scheduler which re-sizes the resource slots, the behavior changes.

I have also tested with the windows option to fix DPI scaling (pics in ZIP) and it works but at the loss of clarity in the browser....

This is a complex issue it seems, more than happy to help with testing if you can find anything. Maybe its something that might need support from Microsoft?

Aleksandar,

Even more testing reveals it works fine in FireFox it seems.

So its only Chrome and Edge (Chromium)  - both latest versions.

Hi Mark,

Thank you for the additional details. I discussed the issue and the details provided with the developer's team and the reported behavior appears to be similar to an issue already reported where some slots in the Scheduler can't be selected and some can:

https://github.com/telerik/kendo-ui-core/issues/4758

The issue suggests as a possible workaround to override the function below: 

kendo.ui.WeekView.fn.selectionByElement= function(cell) {
  var offset = cell.offset();
  return this._slotByPosition(offset.left + 1, offset.top);
}

This is demonstrated in this dojo.

Can you please give the above suggestion a try and let me know if the observed issue is resolved?

Regards,
Aleksandar
Progress Telerik

Thank you - that does seem to fix the week view.

Problem still persists in Day View.

Do you have a similar solution for that?

Hi Mark,

I am glad to hear the suggested workaround helper resolve the WeekView issue. Currently, however, I cannot suggest a workaround for the behavior observed on the DayView. As this issue is quite difficult to reproduce and I am still struggling to reproduce it on either the WeekView or the DayView I will ask you to provide some additional details on the issue observed in the DayView.

I assume you still have the scaling enabled, is that correct? When you select a slot is the above slot being selected or the below slot? Can you share a screencast of the behavior observed on the DayView? This would be helpful in diagnosing the issue further.

Looking forward to hearing back from you.

Regards,
Aleksandar
Progress Telerik

Aleksander,

Thank you for all your help - this fixed it for DayView

kendo.ui.DayView.fn.selectionByElement= function(cell) {
  var offset = cell.offset();
  return this._slotByPosition(offset.left + 1, offset.top);
};

Hopefully that will be the end of the issues.

Hello Mark,

Thank you for sharing the workaround that helped resolve the issue. I am sure it would be beneficial to the community until the issue is fixed.

Regards,
Aleksandar
Progress Telerik