I would like to request a mode for the Kendo React Date and Time Inputs that would allow the use of a mask like that of the MaskedTextBox - allowing the user to type freely without having to make use the arrow keys for each individual date/time part. 

As in the JQuery version, it would be good to have the option of setting min screen width for grid column like below.

https://docs.telerik.com/kendo-ui/api/javascript/ui/grid/configuration/columns.minscreenwidth#columns.minScreenWidth

Currently the GridFilterCell OnChange returns a subset of a FilterDescriptor (A value an an Operator to run on the value), which allows a custom filter cell to create one filter rule (FilterDescriptor). However, the CompositeFilterDescriptor structure allows a lot more flexibility. `month == 'January' OR 'March' OR 'May'`. If the GridFilterCell could be passed a CompositeFilterDescriptor instead of the current subset, then a custom filter cell could be much more powerful.

In an orders grid for instance, with a status of Pending, Paid, Shipped, and Delivered a "Show/Hide Shipped" button would exclude or include the Shipped and Delivered orders when clicked. Or a list of checkboxes to choose the statuses you want to see (like the JQuery Grids support).

TL;DR: There is currently no way to re-implement multi-checkboxes or other complex filtering interfaces with the Kendo React Grid without re-implementing all of the filtering logic manually from scratch, as the Existing filter cells don't support this and a custom GridFilterCell can't be configured to return that logic in a single FilterDescriptor. 

It would be great to have a TreeList component similar in appearance and behavior to the jQuery TreeList (https://demos.telerik.com/kendo-ui/treelist/index), but with the kind of support for virtual scrolling built into the native KendoReact Grid component.

A React wrapper exists for the jQuery TreeList, but it still doesn't play nicely with React, and in any case only supports paging for displaying large data sets, which is inherently not intuitive for displaying tree structures where parent / child hierarchies might span multiple pages.

My sense is this native component would basically be the Grid, but with support for hierarchical data, including drag-and-drop re-ordering of parent / child relationships.

Thanks for considering this feature.

The DatePicker and DateInput React components miss the customizable button to clear the date value.

Would be nice to have ability to customize the icon, size, margins and a selectable option to clear the date value to null or a default value (as set to the component) or bind a custom event handler.

It should have the following functionalities:

Please add the “add widget” functionality as the jQuery version has.
Please add the “remove widget” functionality as the jQuery version has.

https://demos.telerik.com/kendo-ui/tilelayout/add-remove

React v18 has been released.

It appears that KendoReact only supports up to v17 (dependency conflicts if you try to use v18).

Can you please add support for React v18?

Thanks!

The feature request:

Kendo react scheduler: in a week/work week view if an event created with start time at 01:00 and ends at 23:00 for example and displayed only working hours:

the event will not visible until we enable all days hours visible:

The issue is described here:

https://www.telerik.com/forums/kendo-react-scheduler-issue-event-is-not-visible-if-start-date-outside-of-working-hours-range

The footer cell is not accessible. I cant be navigated with the keyboard and isn't read out by the screen reader.  Ideally, we would have all the attributes that the header and content cells have to make this work in the same way.

Create the KendoReact Media Player component.

Similar to the Kendo UI for jQuery component:

https://demos.telerik.com/kendo-ui/mediaplayer/index

We are migrating our legacy application which uses Telerik for Silverlight to react application with KendoReact controls. I am converting one screen which uses RadTreeView which gives us Drag and Drop with Reordering feature. Now, in KendoReact, TreeList control does not provide both the features. 

Here is what we get when we start dragging item in Silverlight control:

I am expecting the same behavior in KendoReact: TreeList as we have to achieve the same behavior in our react application. This link has some discussion with support team.

Thanks,

Hi,

We have requirement of date picker display quarters view . please see the below example

http://jsfiddle.net/4mwk0d5L/1/

Regards,

Susanta

In our unit tests, we sometimes want to be able to use the ByTestId methods of the React Testing Library to find bits of DOM created by a Kendo component.  However, setting a data-testid attribute (or really any data- attribute) on a Kendo component does not always result in the attribute appearing anywhere in the final DOM.

To demonstrate, below is a test suite (also included in the zip) where I tried putting a data-testid attribute on the Kendo components Input, TextArea, Checkbox, Slider, SliderLabel, MultiSelect, and DatePicker, then checked if the attribute appeared in the rendered DOM.  The tests for Input, TextArea, and Checkbox are successful.  The ones for Slider, SliderLabel, MultiSelect, and DatePicker are not.

import { render, screen } from '@testing-library/react';
import { Input, TextArea, Checkbox, Slider, SliderLabel } from '@progress/kendo-react-inputs';
import { MultiSelect } from '@progress/kendo-react-dropdowns';
import { DatePicker } from '@progress/kendo-react-dateinputs';

// SUCCEEDS
describe('Kendo Input', () => {
    it('supports data attributes', () => {
        render(
            <Input data-testid="the-input" />
        );

        const input = screen.queryByTestId('the-input');
        expect(input).toBeTruthy();
    });
});

// SUCCEEDS
describe('Kendo TextArea', () => {
    it('supports data attributes', () => {
        render(
            <TextArea data-testid="the-text-area" />
        );

        const textarea = screen.queryByTestId('the-text-area');
        expect(textarea).toBeTruthy();
    });
});

// SUCCEEDS
describe('Kendo Checkbox', () => {
    it('supports data attributes', () => {
        render(
            <Checkbox label={"Chad"} data-testid="the-checkbox" />
        );

        const checkbox = screen.queryByTestId('the-checkbox');
        expect(checkbox).toBeTruthy();
    });
});

// FAILS
describe('Kendo Slider & SliderLabel', () => {
    it('supports data attributes', () => {
        render(
            <Slider min={1} max={2} data-testid="slider-root">
                <SliderLabel position={1} data-testid="slider-label-1">One Fish</SliderLabel>
                <SliderLabel position={2} data-testid="slider-label-2">Two Fish</SliderLabel>
            </Slider>
        );

        const sliderRoot = screen.queryByTestId('slider-root');
        const sliderLabel1 = screen.queryByTestId('slider-label-1');
        const sliderLabel2 = screen.queryByTestId('slider-label-2');

        // test them all at once so we can know the full scope of our failure/success
        expect({
            sliderRoot,
            sliderLabel1,
            sliderLabel2
        }).toMatchObject({
            sliderRoot:   expect.anything(), // don't be null or undefined
            sliderLabel1: expect.anything(), // don't be null or undefined
            sliderLabel2: expect.anything()  // don't be null or undefined
        });
    });
});

// FAILS
describe('Kendo MultiSelect', () => {
    it('supports data attributes', () => {
        render(
            <MultiSelect data-testid="the-multi-select" />
        );

        const multiselect = screen.queryByTestId('the-multi-select');
        expect(multiselect).toBeTruthy();
    });
});

// FAILS
describe('Kendo DatePicker', () => {
    it('supports data attributes', () => {
        render(
            <DatePicker data-testid="the-date-picker" />
        );

        const datepicker = screen.queryByTestId('the-date-picker');
        expect(datepicker).toBeTruthy();
    });
});

Hello team,

We work on a product that features a large set of input components that are based on the Kendo inputs and dropdowns. We have custom designs that require us to customize the Popups of comboboxes, multi-selects, color pickers, etc with specific layout and styling, open/close animations, blur handling and keyboard interactions (e.g. closing on Esc). This is done fairly easy with the Date Input components (DatePicker, DateTimePicker, DateRangePicker, TimePicker) as they expose such property:

popup?: React.ComponentType<PopupProps>;

However most other controls that use a Popup internally expose just PopupSettings that is not enough for us even with the "appendTo" option.

We would be happy to see a similar ability (as in Date Inputs) to inject the Popup component in:

• Components in the "@progress/kendo-react-dropdowns" package.
  Most of them simply reuse the same ListContainer component that renders the Popup.
• ColorPicker in the "@progress/kendo-react-inputs" package.

I guess that customizing the popup in the DropDownButton, FloatingActionButton and SplitButton would also be nice to have but for those CSS styling does good enough job for us.

Regards