Unplanned
Last Updated: 13 Feb 2025 11:25 by ADMIN
Created by: Ram
Comments: 5
Category: KendoReact
Type: Feature Request
3
Sorting for the MultiColumnComboBox columns - We need the ability to sort list data and allow user to select column to sort.
Unplanned
Last Updated: 11 Feb 2025 14:47 by Andy
Created by: Andy
Comments: 0
Category: Popover
Type: Feature Request
1
The flip now flips from left to right or top to bottom. Can you provide a prop to flip from left to top if there is no space in right and bottom? For example - The record appears in the list view is at the bottom right corner and popover for that last record doesn't have space at the right and bottom, so it flips to top.
Unplanned
Last Updated: 11 Feb 2025 14:33 by Andy
Can you provide an option to display the callout in the middle of the anchor element instead of in the middle of the Popover itself?
Unplanned
Last Updated: 06 Feb 2025 15:30 by ADMIN

in latest v9.3.1 it appears GridFilterCell isn't passing properties shaped as 'isRequired' on DatePicker popupSettings 

this does seem to be a regression because i just recently noticed it in latest upgrade which we need for other bug fixes.

i pursued patching myself by populating animate in GridFilterCell.mjs which seemed to work but then i got warning for the next required property "appendTo". however, populating appendTo yields warning "Warning: Failed prop type: Invalid prop `appendTo` supplied to `Kendo React Popup`. Validation failed." so it's not easily reconcilable that way... therefore i tried removing isRequired on all 3 DatePicker popupSettings properties which of course avoided warnings and i didn't see any negative side effects.

here is a codesandbox repro minimally tweaked to include a date field from kendo grid's "getting started" demo: https://codesandbox.io/p/sandbox/cool-sanne-d4tp85

admittedly this is just a warning but it does create unnecessary noise in browser debug which detracts from issues truly requiring attention during development.

screenshot with the warning from that demo repro:

Unplanned
Last Updated: 31 Jan 2025 10:57 by ADMIN

We are using a customized ChartToolTip with button in our bar chart. However the tab order is not correct for multiple charts. The expect behavior we were told by our accessibility testing team is first chart -> button on tooltip -> second chart -> button on tooltip and so on. The actual behavior is tab shortcut will switch between charts then back to the first chart tooltip element. 

MAS Reference:

Unplanned
Last Updated: 30 Jan 2025 13:07 by ADMIN
Created by: Andrei
Comments: 3
Category: KendoReact
Type: Feature Request
0
I think it would be convenient for users to scroll through tabs not only by clicking on the buttons around the edges, but also by moving their finger across the tabs themselves, which is currently unavailable.
Unplanned
Last Updated: 13 Jan 2025 09:07 by Vaneet
Created by: Vaneet
Comments: 0
Category: KendoReact
Type: Feature Request
1
Kindly help, I need onscroll event or listener to scroll  other pdf's section simultaneously, Right now there no scroll event in pdf-viewer to detect scroll position
Unplanned
Last Updated: 24 Dec 2024 10:56 by n/a
Created by: n/a
Comments: 0
Category: Filter
Type: Feature Request
2

Currently there are only four filter options coming built-in from the Data-Tools library:

- TextFilter - the KendoReact Input component

- NumericFilter - the KendoReact NumericTextBox component

- BooleanFilter - the KendoReact DropDownList component

- DateFilter - the KendoReact DatePicker component

Provide a way to introduce custom filter components

Unplanned
Last Updated: 22 Dec 2024 17:36 by ADMIN
Created by: Hubert
Comments: 1
Category: Menu
Type: Bug Report
0

When there are many items in the menu, the height should not exceed the page size. Now the scroll is not displayed.

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

It refers to version 9.1.0, version 8.5.5 works fine

Thank you

 

Unplanned
Last Updated: 19 Dec 2024 15:44 by ADMIN
Created by: JeffSM
Comments: 1
Category: KendoReact
Type: Feature Request
0
Please would be great a control to read QRCode.
Unplanned
Last Updated: 19 Dec 2024 08:45 by ADMIN
It would be very helpful to be able to format spreadsheet columns with different date formats instead of it automatically reformatting any date input to mm/dd/yyyy. I imagine it would also be useful with number formats as well.
Unplanned
Last Updated: 18 Dec 2024 16:43 by Mark
Created by: Mark
Comments: 0
Category: KendoReact
Type: Feature Request
1

It would be ideal if toODataString could take an additional parameter that:

  1. Takes a collection of expressions,
  2. Each expression takes an Operator and Value,
  3. Each expression returns a string or undefined, where the latter suggests we wish to suppress this expression.

 

Unplanned
Last Updated: 17 Dec 2024 16:52 by ADMIN
Created by: Rajesh
Comments: 1
Category: TreeView
Type: Feature Request
0

Requesting for a load more button feature in tree view similar to the one in kendo Angular Tree View control

https://www.telerik.com/kendo-angular-ui/components/treeview/load-more-button

Unplanned
Last Updated: 17 Dec 2024 11:04 by ADMIN
Created by: Daniel
Comments: 1
Category: KendoReact
Type: Feature Request
1

A json-file is needed to use localization in Kendo React. It's a lot of work to maintain these files when there are new versions. It's difficult to know which keys have been added, changed or removed.

One way that would really help is if you create a way for us to upload our custom-json and then it adds the missing translations, remove those that you have removed, and update the names of those that has been renamed.

Another better way might be that you collect the translation for different languages and let us download them. That way you can also keep them up to date.
Unplanned
Last Updated: 16 Dec 2024 10:45 by pooja
Created by: val
Comments: 3
Category: KendoReact
Type: Feature Request
6
Telerik UI for ASP.NET Core Gantt: https://demos.telerik.com/aspnet-core/gantt/resources. has Planned vs Actual timeline would be great!
Unplanned
Last Updated: 10 Dec 2024 19:28 by ADMIN
Created by: Matthew
Comments: 1
Category: KendoReact
Type: Feature Request
1

Hello! Is it possible to not show a room if there is no meeting on that day while simultaneously showing it on a different person because they have a meeting on that day? In the image below, I edited the data so Peter no longer had a meeting in room 2. Is it possible to get it to show Peter with just the meeting room(s) that they has data for, while keeping Alex with all the rooms that they have data for?

Peter -> Meeting Room 1 

Alex -> Meeting Room 1 AND Meeting Room 2

 

I think this would be a great feature to have. Lets say I have 100 students and/or 100 meeting rooms and all have a different days/times when they are needed. If there was a way to show ONLY what is being booked, or show ONLY what is free, that would be a fantastic feature for users and developers alike. 

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

Unplanned
Last Updated: 09 Dec 2024 08:51 by ADMIN

Hello,

Please add a feature to highlight areas of a PDF on specific pages.  This feature is available in a different library - React PDF Viewer library - but that is apparently no longer supported, and has security vulnerabilities:

https://react-pdf-viewer.dev/examples/render-the-highlight-areas/

This is a critical feature for an application we are building.  Thank you for any assistance.

Unplanned
Last Updated: 28 Nov 2024 07:15 by ADMIN

Hi,

We prefer to have keyboard up/down cursor correspond to navigating input focus up/down a row in the KendoReact Data Grid.

We are already successfully using custom GridColumn Cells to render inputs at all times in tandem with a Grid.onKeyDown handler that finds the next input to set focus.

(for anyone interested this only took a few lines of code to implement a dom navigation heuristic that finds the column index of the nearest TD via onKeyDown event.nativeEvent.target.closest("td") and then finds the corresponding td to that same column index in the next TR up or down, and then hits the first nested native html <input> found to call focus() -  this seems simple and durable to variances in nested components as long as there is a native input to be found, hence the need to render inputs at all times... which does run counter to the approach i saw represented in the KendoReact demos based on setting a particular dataitem's "inEdit" property which wasn't the look we were going for =)

The above cursor navigation is working but before it kicks in, inputs like the DateTimePicker are also taking a cursor up/down to change the date segment that currently has focus - and this doesn't seem to be optional behavior yet?

I believe the fundamental challenge to any dom "wrapper" approach is by the time an outer dom element receives onKeyDown it's too late for event.preventDefault or event.stopPropagation to hide it from the inner input element (the native kendoreact inputs in this case).

Hence the ask here to have an option to ignore that at on the individual KendoReact input components.

With previous KendoReact component builds (e.g. 8.2.0) we successfully proved "patch-package" various subcomponents of DateTimePicker, NumericTextBox and MultiSelect to prevent them from responding to up/down cursor events.

Of course patch-package approach is fragile to upgrades and sure enough recent need to take @progress/kendo-react-dateinputs@9.1.0-develop.6 to get into DateTimePicker formatPlaceholder bug fixes broke previous patches, highlighting need for more resilient fix.

I've attached the latest patch-package files to give precise reference to what keyboard events we're interested in disabling.


I'm assuming this is a feature request and happy to have it reallocated to a support ticket... but wanted to post it in open forums in case community might have alternative suggestions to achieve what we're looking for?

Maybe other approaches to what seems like it could be a general html nested component strategy pattern?

For instance, I'm hesitant to pursue any removeEventListener based approaches for fear of how that might conflict with how i vaguely understand react is continually recreating dom elements upon each render cycle, so i'd be open to encouragement in that direction if anyone has experience to share?

Also wondering if this falls into the realm of "accessibility" and maybe there's already ways to disable accessibility? (as negative as that sounds).

Unplanned
Last Updated: 25 Nov 2024 12:27 by ADMIN

When your window control closes, focus returns to the element that invoked the window unless it is very unlikely users need to immediately reinvoke the window.

We use your window control as a popup search dialog. Our customers search for their data there, close the popup and then return to a dialog with lots of input fields.
The user had previously focused on one of these input fields and would like to have the focus back in this input field after closing the popup.
Which has worked wonderfully up to and including your version 8.0.0.

Unfortunately, this no longer works since version 8.1.0 and instead of the input field, only the button that previously opened the popup is focused. This change from the changelog seems to be responsible for this: "window: update focus management and kb navigation to match the ARIA spec".
It seems that your change uses a setTimeout internally, which keeps taking the focus away from our input field.

You can reproduce this behavior in a demo application. The first application is based on version 8.3.0 and you can reproduce the problem there by pressing the button and closing the opened popup. The focus that was previously in the input field is then on the button. Here: https://stackblitz.com/edit/react-xdpeqc-nycw86?file=app%2Fapp.tsx,package.json
In the second application based on version 8.0.0, you can see that the same process sets the focus directly back to the input field. Here: https://stackblitz.com/edit/react-xdpeqc-yab7m8?file=package.json,app%2Fapp.tsx

Nowhere in the ARIA specification here does it say that you should use a setTimeout to steal the user's focus again at a later time in order to set it on the button that opened the popup. On the contrary, point 2.1 describes exactly what we need:

You already had this feature in version 8.0.0 and could offer it again as a property with very little implementation effort. Please consider to add this old behaviour as a Window Prop again.

Unplanned
Last Updated: 21 Nov 2024 10:55 by ADMIN
Created by: Oliver
Comments: 1
Category: Window
Type: Feature Request
1

If the zoom property is set on the body element for a preset zoom your window control does not seem to correctly take this zoom into account for the position and width/height of the window. You can easily recreate this in the following example application: https://stackblitz.com/edit/react-qmwfbf-fzmj98?file=app%2Fapp.tsx,index.html

Simply open the window using the button and then maximize the window in the title bar at the top. You can see that the width/height calculation is much too large and is not correctly maximized to the available space. You can also see this in the attached video.

A similar problem has already been reported here for popups https://github.com/telerik/kendo-react/issues/2320 and there is also a solution for this using the scale property in the PopupProps here:

<PopupPropsContext.Provider
      value={(props) => ({
        ...props,
        scale: 1.25,
      })}
    >


Please add exactly the same scale property for the WindowProps

1 2 3 4 5 6