Add PDF export in Spreadsheet similar to the one available in the Kendo UI Spreadsheet widget. The PDF export must support multi page export as well.

Add a prop to the MaskedTextBox that returns a clean value (without mask literals) and treats an empty mask as null or "".

This will simplify form validation and submission by eliminating the need for manual cleanup of masked values like ____-____-____-____ or 1234-5678-9012-3456

When the resizing of the Grid is enabled, the expand/collapse column is always resizable.

Currently, the KendoReact DateTimePicker supports passing a DateFormatOptions object to the format prop, but it only respects the datetime property. This prevents developers from using separate localization styles for the date and time portions (e.g., date: "medium", time: "short"), which is supported by the native Intl.DateTimeFormat and toLocaleString APIs.

Currently, there is no option to add a hyperlink to the exported cell.

It would be beneficial if the DatePicker exposed an onKeyDown evet.

It would be beneficial if we had a mechanism for customizing the Chart animations.

Hi,

The first render of a DatePicker component with an onOpen prop throws an error: Unknown event handler property `onOpen`. It will be ignored.

Reproduction:

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

2. The error will appear in the console

Expected behavior:

No errors in the console

I would like to be able to customize the collapse action on a splitter pane. The specific use case is to be able to collapse a splitter to a minimum width, and when it is at the minimum width the collapse icon switches to expand. I have been able to create a workaround by intercepting the state change and setting a pane to a minimum width when the collapsed property changes. It requires some complex state checking code, and there is no way to switch the icon. There are a number of ways that this could be accomplished by exposing more props to give developers more flexibility with the collapse icon click. Thanks.

Hello,

there are numerous problems with navigating / scrolling on the DataGrid using keyboard keys.

Here is the test page:

https://stackblitz.com/edit/react-brdhufzd

 

1. Grid with navigatable=true:

- arrow keys - when you select a cell to be able to navigate and then  keep pressing down and then up, it's not posible to come back to the first record. You need to use the mouse.

- Page up/down keys work the other way round, also sometimes is not possible to come back to the first record, the scrollbar does not show the current position.

- It starts to work correctly after using the arrow keys and page up/down keys alternatively couple of times

2. Grid with navigatable=false:
- arrow,Page up/down keys and scrollbar work correctly

3. Grid with navigatable=true and nested inside Window:
- works the same way as not nested - the same problems occur

4. Grid with navigatable=false and nested inside Window:
- arrow keys move the window instead of navigating the grid
- Page up/down don't work at all

Hello

Localization messages for ColorPicker popup Apply/Cancel are missed.

Option to hide does not work flatColorPickerSettings={{showButtons: false}}

 

stackblitz

 

Hi Telerik Team,

I'm exploring options for implementing a data visualization feature in a feature project and was considering using KendoReact Bar Chart component.

I wanted to know if KendoReact currently supports -- or plans to support -- editable or user-modifiable bar charts? Specifically, I'm looking for functionality where users can click or drag a bar to their desired value, allowing for a direct manipulation of chart values.

I've seen the existing interactive features (i.e. tooltips, hover effects, selection), but I'm referring to a more hands-on editing capability to support both a visual and input interface.

This would be a useful feature for me and my team. I would like to know if anything like this is on your roadmap.

Thank you your time.

Best regards,

Irma Leandre
Research Engineer / Assessment Technology Solutions (ATS)

 

[email protected]

Currently, when we pass an empty string ("") or leave the title undefined for a GridColumn, the Grid automatically falls back to rendering the column's field name as the header title (inside the .k-column-title span).

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

Provide the RecurrenceEditor as a standalone component, enabling developers to integrate recurrence rule editing independently of the Scheduler.

Allow customization of the top-right icon in the Adaptive View header (DatePicker and DateTimePicker)

Currently, the Cancel button resets the internal state but does not close the popup, which confuses users.

Hi,

Is there any way to configure the horizontal spacing of the Kendo React OrgChart?  When I render the chart there are huge gaps in between the cards.. I have enclosed a screenshot below.  It appears that the space given to each "column" is the same (is determined by the "widest" column, on the left in my diagram).

This is really unpleasant and unusable.  I see from Google searches that the Kendo jQuery component suffers the same problem.  I really hope you can help me resolve this or publish a fix soon.  This OrgChart component is one of the reasons I purchased the suite, and it is disappointing to uncover this problem after my trial.

thanks, Derek

Good morning,

I have seen a component within the Angular library that I would like to include in my project using React. The link to it is here:

https://www.telerik.com/kendo-angular-ui/components/dropdowns/dropdownlist/add-new-item

Are you able to advise on how I could implement this please?

 

Best wishes,

Molly

Please consider adding support for virtualization (e.g., virtual settings or similar) to the GridColumnMenuCheckboxFilter so that it can efficiently handle large datasets without performance hits.

Benefits:
 - Better performance with large datasets
 - Consistent UX with existing Kendo filtering components
 - Reduced need for custom workarounds