In Multicombobox choosing combo element using keyboard is broken when data source contains more than one duplicate value of a property used as a textField.

Steps to reproduce:

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

2. Try to select the 4th value using the arrow keys.

It's impossible because there are two items with the name 'Guy Wooten,' and this field is used as the textField.

Several months ago, I used this example to hide the default row detail expander, and implement my own custom expander:

https://www.telerik.com/kendo-react-ui/components/knowledge-base/custom-expand-collapse-column

As you can see, it seems that some upgrade along the way has broken the example, and it now shows two expander columns. This is also happening when i attempt to upgrade the version in my project. Can this be fixed, or is there a new workaround?

Description

PivotGrid does can not export all the date to excel when the nodes are collapsed

Plan

KendoReact Free

Steps To Reproduce

https://www.telerik.com/kendo-react-ui/components/pivotgrid/excel
Configure a PivotGrid with multiple row and column fields, and at least one measure.

Expand only a few nodes manually.

Click the Export to Excel button.

The exported file contains only the visible/expanded rows/columns.

Screenshots or video

No response

Actual Behavior

It is not practical or user-friendly to expect users to manually expand every node (especially if data changes frequently).

Users expect complete data export based on the selected dimensions/measures and based on provided data source to generate pivot grid — not just what is visible.

Expected Behavior

Expected Behavior:
When clicking Export to Excel, PivotGrid the entire dataset should be exported in expanded format.

Browser

Chrome, All

Browser version

latest

OS type

MacOS

OS version

No response

Last working version of the KendoReact package (if regression).

No response

We use data grids with virtual scrolling for inline editing a large number of records. However, when we want to add a new row to the grid it automatically resets the scroll position and doesn't even fire onPageChange event so the records you see do not correspond to the scroll position.

Check the following example (scroll to bottom, click anywhere on the table - this will add a new row - and observe the described problem):

https://stackblitz.com/edit/react-52zzvz?file=app%2Fapp.tsx%3AL78

I have noticed that whenever you want to upload multiple photos at once, using this React Upload Component & Events - KendoReact Docs & Demos (telerik.com) component the previews of the images uploaded bounce/ shake around. I've tried this on multiple browsers and they all have the same bouncing effect for the image previews. For a single photo it doesn't do it but once multiple images are added, it will do it.

As per the subject. This can be observed in the following StackBlitz which is forked from the Telerik documentation on resizing with three small changes:

• Remove style={{ height: '400px' }} from the Grid component in app.tsx
• Remove height: 100%; from my-app style in index.html
• Remove height: 100%; from html, body style in index.html

https://stackblitz.com/edit/react-vajzshwv?file=app%2Fapp.tsx,index.html

Logged as a bug because there is nothing in the documentation stating that a height for the Grid or Grid container must be set in order for this to work. If this is a documentation issue rather than a code issue, please advise the recommended approach for using the Grid resizable property.

Hi,

I have run into an issue when trying to input a date value where its parts contain a leading 0. The autoCorrectPaths option is set to false and I have specified a date format in my datePicker component. 

Reproduction:

1. open https://stackblitz.com/edit/react-wz6zocpe?file=app%2Fapp.jsx

2. try to input a date by typing 09, then 03, then 2025

Expected behaviour:

The date in the input field should be "09.03.2025"

Actual behaviour:

The date in the input field is "day.09.2000"

As stated in the subject, the GridNoRecords component has an undocumented maximum width of 20em after which the GridNoRecords message is cut off. Please see the following StackBlitz for an example: https://stackblitz.com/edit/react-2z8hh63r?file=app%2Fapp.tsx

Kind regards,

David

To demonstrate:

1. Open your simplest interactivity/selection demo, which is not grouped, in StackBlitz. See: https://www.telerik.com/kendo-react-ui/components/grid/interactivity/selection/

2. Add the Grid's group prop. To demonstrate the bug nothing else needs changed

<Grid group={[]} ...

3. Run demo, scroll down and pick a row.

4. Observe the grid scrolls to the top and you cannot see your selected row unless you scroll back.

Setting the stage prop to "DEFAULT" does not update the Window component as expected:

const [stage, setStage] = React.useState<string>('DEFAULT');  

const handleStageChange = (e: WindowActionsEvent) => {
    setStage('DEFAULT');
  };

<Window
          stage={stage}
          onStageChange={handleStageChange}

Setting the window position is not permanent.

How to reproduce:

1. open https://stackblitz.com/edit/react-hyhjxg?file=app%2Fapp.tsx
2. click 'move to corner' button
3. click the window title bar
4. the window changes its position to the previous one, but it should remain in place.

Chaging window stage also reverts previous position

Hello,

We have recently upgraded our packages to version: "@progress/kendo-react-grid": "^6.1.0". While testing the new look and feel of the application we've noticed that the pagination is no longer working on several grids from the application. After investigating for a while, we have found the property that is causing the issue(rowHeight), please take a look at the Stackblitz example from below.

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

As you can see, in the example the pagination is not working. If we remove the property "rowHeight" from the grid the pagination is working again. We are not sure how these two are related but can you tell us what is going wrong and how we can fix it?

Thanks!

Dear sir/madam,

We noticed an error when setting the "defaultShowWorkHours" to false, it still shows the work hours as the default.
Check the Codesandbox

Expected behavior when you set "defaultShowWorkHours" to false, it shows the full day timeline

Hi, Keyboard navigation using "page down" and "page up keys" doesn't work.

Here is a stackblitz where the problem can be reproduced: https://stackblitz.com/edit/react-q9n5fe?file=app%2Fmain.tsx
Reproduction steps:

1. Click inside the grid
2. Press "Page down" or "Page up" - doesn't work

It only works when:

1. Click outside of the grid
2. click on vertical scroll bar without selecting any grid cell.
3. Press"Page down" or "Page up" - it works.

Best Regards

Hubert

I'm submitting a...

• Bug report

Current behavior

When importing Excel files that contain values with a currency formatting, the currency signs are not displayed correctly.

Expected behavior

When importing an Excel file, the data displayed in the Spreadsheet component should look the same way as in the imported document.

Minimal reproduction of the problem with instructions

1. Download this SampleData.xlsx file
2. Go to this example from the documentation
3. Click on "File -> Folder Icon"
4. In the popup select the downloaded file and import it

Environment

Package versions:
KendoReact 8.0.0