I am using conditional rendering to render a custom editor for the resources in the Scheduler. Even if there is no resource editor the label still renders. 

I'm submitting a...

• Feature request

Current behavior

Timepicker component with no value set has its popup after opening scrolled to minimal value, eg. 00:00.

Requested behavior

Requested behavior would be that the component allows to set value to which should the popup be scrolled after opening, when the component has no value set.

What is the motivation or use case for changing the behavior?

When user e.g. records his work hours, in most cases his work starts at the morning or at the current time. With current behavior the user needs to scroll every time to value he needs to set.

I would like to extend the functionality of the chart wizard. For example, if I wanted to expose other things to change about the chart, could I create a new tab in the wizard? I would like to allow the user to turn on and off things and I think it makes the most sense to put this functionality next to the other tools editing the chart.

Hi,

At present the KendoReact Dialog is not responsive i.e. if the Dialog height is greater than the viewport height, the Dialog Action Buttons are not accessible e.g. https://stackblitz.com/edit/react-qcenpnxr?file=app%2Fapp.tsx

I have made a custom control to deal with this that attaches a resize event handler to the window, but there is no good way to add the viewport width and height as max dimensions to the Dialog:

• style - applied to the "k-dialog-wrapper" div, any use of dimensions here completely ruins the presentation of the Dialog
• contentStyle - applied to the "k-window-content k-dialog-content" div, does not prevent the Title or Action Buttons from exceeding viewport dimensions
• ref - DialogHandle with "k-dialog-wrapper" div as the element

In order to make a responsive Dialog I have to take a ref to get the "k-dialog-wrapper" div, use a querySelector to get the "k-window k-dialog" div, and set the maxWidth and maxHeight styles there.

Unless there is a better way to achieve this, it would be good if the Dialog was responsive out of the box, or at the very least exposed maxWidth and maxHeight props directly.

Kind regards,

David

I'm submitting a...

• Bug report

Current behavior

Timepicker component in adaptive mode behaves differently in version 11.0.0 (and above) compared to version 10.0.0 (and above):

• "Set" button sets value but does not close popup - one more click needed
• "NOW" button scrolls to current time, but does neither set value nor close the popup - two more clicks needed
• in the top right corner there is a button with check icon which does the only thing - closes the popup (the same as "Close" button) - it is confusing

Expected behavior

We would expect the same behavior as in the 10.0.0:

• "Set" button sets value and closes the popup
• "NOW" button scrolls to current time, sets value and closes the popup
• there are no two buttons with the same functionality

Minimal reproduction of the problem with instructions

1. Please run following link: https://stackblitz.com/edit/react-j3smansk?file=app%2Fapp.tsx,package.json and adjust app container width so that the timepicker popup is rendered in the bottom half of the screen, allowing both the popup and the editor to be visible at the same time. 
2. Repeat previous step for following link: https://stackblitz.com/edit/react-ukfuqrdy?file=package.json,app%2Fapp.tsx
3. As you can see in "app.tsx" examples are very the same (taken from https://www.telerik.com/kendo-react-ui/components/dateinputs/timepicker/adaptive-rendering), only versions of kendo-react components in "package.json" are different
4. Observe situations described in Current behavior and Expected behavior sections

What is the motivation or use case for changing the behavior?

We would like to upgrade to 11.0.0 but we do not like this behaviour because it is disturbing, confusing and requires more clicks (time) to work with it.

Environment

Browser:

• Chrome (desktop) version 138.0.7204.50 (Official build) (64-bit)
• Firefox version 140.0 (64-bit)
• Edge Version 137.0.3296.93 (Official build) (64-bit)

System:

• TypeScript version: KendoReact demos page version
• Node version: KendoReact demos page version
• Platform: Windows 10

Best regards,

Peter

Hi, 

After pasting a value into the input box of the DatePicker I am then unable to clear it. The value of the DatePicker is correctly set to null, but the value displayed in the input box is unchanged.

Reproduction steps:

1. Open the grid filtering demo,

2. Copy any of the date values from the grid, e.g. 9/20/1996, and paste it into the "First Ordered On" filter,

3. Clear the filter using the clear button.

Result:

The value remains in the input box.

Expected behaviour:

The value should not be visible in the input box.

 

 

Currently the GridColumn Component only supports width property.  It should also support minWidth and maxWidth properties for better responsive design.  https://www.telerik.com/kendo-react-ui/components/grid/api/GridColumnProps/

*** Support ticket created by Telerik by Progress staff ***
*** Please follow-up with additional details, if necessary. Thank you. ***

The KendoReact Scheduler currently does not provide a supported way to display only all-day events while hiding all time slots when using vertical resource grouping (Week or Timeline-based views). It would be beneficial if we had a mechanism for implementing an all-day–only Scheduler view that supports vertical resource grouping, renders multi-day events as a single continuous bar across consecutive days, and preserves the existing Scheduler structure and interactions.

It would be beneficial for GridToolbarColumnsChooser to offer customization options that allow developers to control which columns can be shown or hidden.

Hi
We use the chart wizard in our app to allow our end users to create their own charts by storing the chart wizard settings and then displaying the chart with updated data.
This works very well.
However there are some limitations with the chart wizard settings that result in us not being able to create as clean and readable charts as we would like. These are:

- In a bar chart the borders of each bar are black irrespective of the colour of the bar. This creates messy charts when have lots of bars that end up being next to each other as only see the black borders and not the (say) red bars. Ideally there should be no bar border

- You can't set the frequency of the x axis labels and hence with lots of items the labels overlap

- You can't have mixed series types i.e. choose type (line, column etc) for each series

The other usage issue is that if you change chart type from (say) bars to columns you loose your settings (eg which data items selected) even though only changing chart orientation

The Data Grid does not work properly with large datasets. In the example below with one million records, it is impossible to scroll to the bottom of the grid.

Firefox: Rows fail to render after scrolling past approximately 200,000 rows.

Chrome: Rows do render, but the skip parameter never exceeds 745,645 even when the scrollbar is at the bottom, preventing access to the remaining ~254,000 records.

This contradicts the documentation's claim that the grid "scales from hundreds to millions of records while maintaining a responsive user experience."

 

https://stackblitz.com/edit/react-aaxnyzxm?file=app%2Fapp.tsx

Please see the example - https://codesandbox.io/p/sandbox/silly-wind-tpfg8n

When column "Unit Price" is locked, while moving the horizontal scroll bar, the group header is sticky (expected behavior), but the group footer is not sticky (wrong behavior).

When using KendoReact Grid with multiple grouping levels, the Grid automatically adds horizontal indentation inside <td> elements to represent group hierarchy.

While this behavior is expected, there is no public API to control, customize, or disable this indentation.
As grouping depth increases, this extra space causes layout issues, unexpected horizontal overflow, and breaks strict or custom design systems.

Is there a reason why this spacing is not configurable?
Are there plans to expose an official option (e.g. groupIndent / groupPadding) or any supported API to manage grouped row indentation?

Example:

Description

User Impact:
Screen reader users will miss important descriptive details on the pager section, making navigation unclear.
This can lead to confusion and difficulty in understanding page context or available actions.

Plan

KendoReact

Steps To Reproduce

Open the URL: https://www.telerik.com/kendo-react-ui/components/grid in edge browser in windows.

'React Data Grid Overview' page will be open.

Press tab key to navigate to the pager section.

Verify whether screen reader is announcing descriptive information on the pager section in windows or not.

Currently, there is no option to utilize controlled mode for the Spreasheet data. The current workaround is to set the defaultProps and then re-initialize the Spreadsheet using the "key" prop. 

Hi,

Currently, the vertical menu/tree component lacks keyboard navigation using arrow keys when the menu options exceed the visible screen area. Users who are not familiar with or comfortable using scrollbars face difficulty navigating through lengthy menus.

Problem Statement:

• Large vertical menus that extend beyond screen height require scrollbar usage

• Not all users are familiar with scrollbar navigation

• Poor user experience for keyboard-reliant users

Proposed Solution:

Add an enable/disable configuration option for arrow key navigation that allows:

• Up/Down arrow keys to navigate through menu items

• Auto-scroll behavior when reaching menu boundaries

• Enter/Space key to select items

• Configurable option to enable/disable this feature

Attached is the screenshot of desired feature on tree (just for reference).

DateTimePicker - TRL support in case of no value - "שנה/חודש/יום" instead of "יום/חודש/שנה"  when the format is YYYY/MM/DD