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.

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

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. 

It would be great if there was an animationClass prop that will make styling easier.

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

Provide a set of utility functions for safely creating, traversing, updating, and deleting filters inside nested CompositeFilterDescriptor trees.

It would be great if there was a way to customize the flag of the Timeline component

It would be beneficial if there was a mechanism to identify the actual grouping level of each header cell regardless of expansion state, such as exposing a groupLevel property

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

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

I want to achieve an improved customization over the font styling of the title and subtitle pieces using the SCSS theme variables. We want to globalize the style changes via SCSS

It would be beneficial if the ExpansionPanel had allowed adding additional header content outside of the built-in title and indicator elements

It would be great if there was a mechanism for customizing the sorting of the ExpansionPanel headers

We should enable the Treelist not to count items on the second level.

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

It would be beneficial if the Chat component had an `allowDuplicates` prop that would prevent the duplication of uploaded files.

We are using the DateFilter from kendo-react-data-tools to filter Odata Edm.Date fields. Neither the DateFilter nor the Edm.Date fields have a time component, but toODataString from kendo-data-query turns the DateFilter value into a DateTimeOffset e.g. YYYY-MM-DDT00:00:00.000Z.

Is it possible to get a date-only value from toODataString using DateFilter?

It would be great if the MultiSelect component had a valueMap prop exposed.

It would be beneficial if we had a kendoSchedulerSlotSelectable exposed similar to Angular.

It would be beneficial if the DateTimePicker had a togglebutton prop so that the button is customizable.