Reproducible in the Events demo.
Also reproducible when selecting the slots from right to left (Wed to Mon) and then selecting the last slot (Mon).
The behavior is identical when selecting slots in a specific day, e.g. selecting and dragging from 8:00 to 10:00 and then selecting the last slot (9:30-10:00).
The change event does not fire.
The change event fires.
In Scheduler event, if the eventTemplate has a table, the add event is triggered when editing an existing task, resulting that both popups open and close instantly.
Open this dojo example. Choose an event and click the span containing the text "I have some icons here".
The add event popup shows together with the edit event popup.
Only the edit event popup should be displayed.
When the user tries to set a repeat rule for an event, the spinners for the NumericTextBoxes are not displayed
The spinners are not displayed. Also, the calendar icon is not displayed.
The following classes should be applied only to the parent element: k-recur-interval, k-recur-count, k-recur-until
The spinners and the calendar icon should be visible
edit: function(e){
$('[name="recurrenceRule"] .k-button-group-stretched button').click(function(){
$('.k-recur-interval.k-input-inner').removeClass('k-recur-interval')
$('.k-recur-count.k-input-inner').removeClass('k-recur-count')
$('.k-recur-until.k-input-inner').removeClass('k-recur-until')
})
},
Dojo - https://dojo.telerik.com/@NeliK/iVExeNek
If you resize the DevTools pane after destroying the Scheduler, a "Cannot read properties of null (reading 'getKendoToolBar')" error is thrown.
Regression introduced with 2022.2.621
An error is thrown after resizing the pane.
No error should be thrown after resizing the pane.
When a recurring event is created in a Scheduler and the id is not set to the event, then if the event is deleted an error is thrown in the console.
3.1. 'kendo.all.js:311085 Uncaught TypeError: Cannot read properties of undefined (reading 'startTimezone')' is thrown
3.2. 'Uncaught TypeError: Cannot read properties of undefined (reading recurrence exception)' is thrown in the console
There should be no errors in the console although the deleted event is without id being set. There could be some more descriptive message.
When the mobile option of the Scheduler is set to true and the user double click/double-tap the Edit dialog is opened, but when saving the event, the following error is thrown in the console:
'Cannot read property 'isOccurrence' of undefined'
An error is thrown in the console (screencast)
There should be no error in the console
When no height is set to the Scheduler the grouping does not expand in height to the rendered month views.
Actual: https://dojo.telerik.com/UhoxowEh
Expected: https://dojo.telerik.com/UPiGosik
### Bug report
When typing in the built-in search box of the Scheduler, the spacebar does not insert a blank space as expected.
### Reproduction of the problem
Type in any word in the search tool and press the spacebar.
A Dojo sample for reproduction: https://demos.telerik.com/kendo-ui/scheduler/search-events
When using Kendo version 2021.3.1109 in the same scenario, the spacebar opens the Popup form for event editing.
A Dojo sample for reproduction: https://dojo.telerik.com/irUKIsEc
### Expected/desired behavior
When you press the spacebar, it should insert a blank space.
### Environment
* **Kendo UI version: 2022.2.510
* **jQuery version: 1.12.4
* **Browser: [all]
Hi,
I'm having some erratic behavior when displaying recurring events in the scheduler when the browser is Safari and in other browsers when the device is an ipad.
The recurring events don't show on the presentation table, but if I force several clicks in the presentation table with the intention of creating a new event and then canceling, they sometimes are rendered in the right slots. After they are rendered if I click the presentation table they disappear again.
If I check the scheduler dataSource data the events are there to be shown.
I tried to replicate the same behavior with the scheduler demo that you have available and I couldn't replicate it. But then I realized that in my case only recurring events won't show up. My hint was that the problem was with the recurrence rule. I created a dojo sample with my recurrence rule and then the bug appeared.
Concluding it seems that for some recurrence rules the recurring events may have problems to be rendered in the presentation table.
Here is a dojo sample replicating the problem that I describe:
https://dojo.telerik.com/USiLEXAk
How can I resolve this problem or have a potential fix?
Kind regards,
Marco Miranda.
When the slotByElement method is used for multiple elements this could lead to performance issues in Scheduler.
For example, the difference in the performance can be observed in the Dojo examples linked below when loading the Scheduler and when changing the selected resources:
Dojo with 2023.1.314 - https://dojo.telerik.com/@NeliKondova/UJOcEJoC
Dojo with 2023.1.425 - https://dojo.telerik.com/@NeliKondova/UHisivuC
The issue occurs starting with the 2023 R1 SP1 release and could be due to the following fix - #7260
Scheduler events in TimeLine view are displayed incorrectly when they start/end at the same time.
Run this dojo
Notice that Event 2 is displayed below Event 1, even though they do not overlap. Removing Event 3 results in Event 1 and 2 being rendered next to one another.
Event 2 should be displayed next to Event 1, but not below, as they do not overlap
It would be great to be able to customize the scheduler's toolbar, either by specify custom buttons and actions through 'toolbar' option or by providing a custom template.
I just upgraded to the latest version today.
kendoScheduler doesn't fire change event when in "Year" view.
This is really easy to duplicate. Select Year and it doesn't fire.
<!DOCTYPE html>
<html>
This one is reproducible on the demo site today and that’s where this screenshot is from. Begin to create a new event. Set to recurring Monthly. Note that below “Never” is checked and the “10/11/2020” box is disabled. Now go and change your start date to any other date above. This box enables itself. It should not do this because the ending date option is not actually selected.
I fixed this in JavaScript by hooking into some events rather than modifying the Kendo.all.js file.
Editing a recurrent event in the Scheduler with End options set to Never
triggers validation on the DatePicker.
This is a regression introduced with R1 of 2022
Never
.Validation error is displayed.
screencast
Validation error should not be present in this scenario.
The recurring events are not rendered as expected in some scenarios depending on the start time set.
The first event is not rendered for every week, but it is rendered for every second week.
When the recurring rule is 'FREQ=WEEKLY' the event should be displayed every week, despite of its starting time.
In 2020 R1 SP2 (2020.1.406) there is a bug related to missing events fixed with 2020.2.513. - Dojo with 2020.1.406
Starting with 2020 R2 (2020.2.513) the current behavior is introduced.
The issue might be related also to: #5978
When the dataSource for the resources is empty and the Month view is selected the 'Cannot read property 'firstChild' of undefined error is thrown in Scheduler.
'Cannot read property 'firstChild' of undefined error is thrown in Scheduler when the Month view is selected.
No error should be thrown with an empty resources dataSource in Scheduler.
The issue is a regression starting with 2020 R1 (2020.1.114) release
When you right click on an event to open a ContextMenu in the Scheduler, the first row is selected.
Regression introduced with 2022.1.301
The first row is selected
The targeted row should be selected
I have a need to create an event that will indicate a resources availability. This only needs to be a thin coloured block. Actual events will then be created along side the 'Availability' block. Basically we have the ability to create an event template. Need to be able to create two have assign the correct template based on what type of event it is. Also need the availability event to be rendered first so that it is always to the left on vertical views and at the top in horizontal views.
Currently, the moveEnd handler contains e.slot and e.resources objects to provide information about the slot where the event was dropped. Please add the corresponding fields to the moveStart handler to identify where the move began.