I would like to request a new Kendo React Grid column editing option so that users can navigate editable columns using the keyboard. This feature should be similar to "navigatable" option from Kendo jQuery grid example - https://demos.telerik.com/kendo-ui/grid/editing

Thanks.

A Wizard Control, allowing any number or steps vertical or horizontal plus ability to modify the look and feel of the steps.  Also the ability to add other controls within each step.  For example a wizard control with the ability to have 3 steps, in which one would have a grid, or scheduler or other components.

We have recently added the scrollable prop to our tabStrip component but we are noticing that now on the active tabs there is a line, which is not show when not using the scrollable property. Is there anyway to remove this line? It makes it more difficult in terms of affordance and UX to see that this element is the active tab when there is this line. It somehow breaks the connection between the tab and the content. 


Any help would be appreciated. 

Hello,

We are currently developing an application based on Kendo React components.
We are wondering if the React-Gantt chart has the functionality to edit the data by drag-n-drop the same way it possible with JQuery-Gantt (see attachment).

Thanks in advance for your help.

 

Kind regards,
Sergei

It would be beneficial if the Chat component had an `autoFocus` prop

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

Disabling the row click selection will be useful In scenarios like multi-row checkbox selection, where the client does not want to update the selection state on row click (but only on checkbox click).

Add an optional row-based keyboard navigation mode for the KendoReact Grid where Arrow Up and Arrow Down move focus between entire rows instead of individual cells.

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.

*** 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.

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.

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

 

The Kendo Form component internally uses a FormContext which is ued by FormElement and Field. However this Context is not exported in @progress/kendo-react-form

Please export this context. It would really help with the usability of the Form component for complex forms. There are things in the FormContext that are not available in the formRenderProps.

Alternatively, put everything from the context into the FormRenderProps. These don't seem like they needed to be 2 different objects.

Specifically with the Context you can see what fields have been `touched`, `visited` and `modified`. But with the render props you only get a boolean if any field has been touched, visited or modified; not the names of the fields.

Be able to to modify the cut-off point depending on what baseUnit is selected in a chart time series.

e.g.

Given the following data points:

Data = [

  Friday 10th Oct: 123,

  Saturday 11th Oct: 54,

  Sunday 12th Oct: 77,

  …,

  Tuesday 20th January: 10,

]

If baseUnit = year

Currently what happens is:

1st Jan -> 1st Jan -> 1st Jan

What we want:

10th Oct -> 10th Oct -> 10th Oct

If baseUnit = month

Currently what happens is:

1st Oct -> 1st Nov -> 1st Dec

What we want:

10th Oct -> 10th Nov -> 10th Dec -> etc

*Edge case of 29th, 30th, and 31st:

Default to last day of the month

Oct 31st -> Nov 30th -> Dec 31st

If baseUnit = week

Currently what happens is:

Sunday 5th Oct -> Sunday 12th Oct -> Sunday 19th Oct

What we want:

Friday 10th Oct -> Friday 17th Oct -> Friday 24th Oct -> etc

If baseUnit = day

This is our minimum unit so everything works

In our software we want to create a filter with MultiSelectTree. The hierarchy is this: LV1 -> LV2 -> LV3. In the database the data is assigned to LV3. If the component is loaded with lot of LV3 items then selecting the parent LV2 node will result a very long tag list in the textbox part of the MultiSelectTree which is not user friendly. In this case I expect selecting the LV2 node will check the LV3 subnodes also but the textbox part has only that LV2 tag as selected. So the checkboxes should remain the same textbox should display the selected parent only.

Other cases:

- when LV1 is selected, then every children will be checked but textbox should display only the selected location

- when 99 of 100 LV3 items are checked then LV2 parent is not fully checked so textbox should display only the bins but only the first N items then use ... characters.

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.