Hi,

I would appreciate if the GridColumnMenuCheckboxFilter will expose an event that can be intercepted when clicking the three dots.

Thank you.

Regards.

 

Hello Team,

I've gone through a requirement like Multicolumn combo box should allow to multiple selection, but it's not available as of now, could you guys please consider it as feature request, MultiColumn should allow multiple selection.

Multiselect with Multicolumn combo box | View Ticket | Your Account

 

Thanks & Regards -

Revanth

Hey Progress,

We're loving KendoReact. Great work!

Regarding Ticket 1680673, would you please add more Flexbox properties to the StackLayout component? Especially justify-contnent: space-between;.

More specs available at https://developer.mozilla.org/en-US/docs/Web/CSS/justify-content.

Regards,

Carey Best

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. 

I am using KendoReact 10.2 and I am getting several warnings about deprecated Sass methods and syntax including one that is causing an error in the browser and blocks rendering. I used the sass-migrator to try to migrate these methods.

Please upgrade KendoReact so it can work with the latest Vite, React and scss/sass packages without deprecation warnings and errors.
Also fix the React version dropdown in this feedback form. It doesn't show React 19 as an option.

Hi,

Add this feature.

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

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

We use "@progress/kendo-react-treelist": "^5.10.1" in our project. Trees are usually placed in flexible containers, and users can reduce their size to 0. At this point, we get an error when calling the tableRowsVirtualization function. I have attached a screenshot at the moment of debugging. You can see that the values of items[0] and lastItem are undefined when the container size approaches 0. I didn't prepare an example to reproduce the error, because I think it's pretty clear that an error occurs here. So the questions are: if this is a bug, is it fixed in the new versions of the package? If there is a possible error on our part or it has not been fixed in the new versions, then what should we do to solve the problem? Thanks

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

 

The Data Grid does not work properly with large datasets. In the example below with one million records, it is impossible to scroll to the bottom of the grid.

Firefox: Rows fail to render after scrolling past approximately 200,000 rows.

Chrome: Rows do render, but the skip parameter never exceeds 745,645 even when the scrollbar is at the bottom, preventing access to the remaining ~254,000 records.

This contradicts the documentation's claim that the grid "scales from hundreds to millions of records while maintaining a responsive user experience."

 

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

Hi, 

After pasting a value into the input box of the DatePicker I am then unable to clear it. The value of the DatePicker is correctly set to null, but the value displayed in the input box is unchanged.

Reproduction steps:

1. Open the grid filtering demo,

2. Copy any of the date values from the grid, e.g. 9/20/1996, and paste it into the "First Ordered On" filter,

3. Clear the filter using the clear button.

Result:

The value remains in the input box.

Expected behaviour:

The value should not be visible in the input box.

 

 

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.