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.
Setting the window position is not permanent.
How to reproduce:
Chaging window stage also reverts previous position
When typing into a date picker and trying to type Feb 29th, 2024 (or any other leap year ofc) the date is updated incorrectly by the kendo date picker validation. As the user types the year their previous entry of 29 is updated to 28. This should update check should probably not occur until the user is done updating the input. If there is some fix or workaround we can do on our end to resolve this issue please let us know
Here's a video of the bug in our application
However, I was also able to reproduce the exact same behavior even in the documentation:
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
Hi team,
Im my example (see here), I've added a 'name' attribute to the 'Persons' resource data, and changed the textField mapping to use the 'name' field, however the scheduler is still displaying the results of the 'text' attribute.
Leading me to think that the scheduler is hardcoded to only look for the text attribute, because if its changed/removed, the scheudler does not display anything, regardless of what the 'textField' value is.
Please advise.
Thanks,
Grant
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:
It only works when:
Best Regards
Hubert
Trying to drag an event in the scheduler duplicates (doubles) the event drag hints, but only in DayView.
Reproduction:
https://codesandbox.io/p/sandbox/still-cloud-xrrx72?file=%2Fapp%2Fmain.tsx%3A21%2C26
Workaround:
The problem occurs when the event data doesn't have isAllDay property set. Even if you simply set it to false seems to resolve the issue. Problem is - Kendo's docs say that "The DataItem type does not limit the user to a specific fields in the data array", however the presence of this field is mandatory for the proper functioning of the DayView.
When importing Excel files that contain values with a currency formatting, the currency signs are not displayed correctly.
When importing an Excel file, the data displayed in the Spreadsheet component should look the same way as in the imported document.
Package versions:
KendoReact 8.0.0
Hello,
We are encountering an issue with duplicate entries in our Kendo Grid with drag & drop functionality. When the grid is scrolled, clicking on any of the header cells multiple times results in the first entry being duplicated. This problem occurs on the example provided on your website as well: Kendo React Grid Row Reordering
Reproduction Steps:
You will notice that the first entry is duplicated multiple times. It appears that the reorder logic is being triggered when a header cell is pressed.
We are using version 6.1.0. Please refer to the attached video for a visual representation of the issue.
Thank you for your assistance.
Actual Result:
After invoking 'table' button, user is unable to select the size of the table i.e, Keyboard focus is not going to 'Insert row and column cell components.
Tab index property is not defined.
Expected
Control(s) must be accessible to keyboards and other assistive technology. Common causes of this problem include a) the element does not have a proper role assigned, b) the element needs tab-index="0" attribute to be focusable, or c) the component is not registering keypresses.
User should be able to navigate to insert row and column cell components to select the size of the table.
User Impact
When interactive components are not accessible, assistive technology users are blocked, which leads to everything from inaccessible content, features, and functionality, up to entire applications or sites.
Hello,
We've been experiencing a weird behavior with the date picker element. We wanted to have an auto advancing cursor that moves from date -> month -> year without the user having to manually press the arrow keys.
We based our solution off this previous method in your JQuery element. However the React element has some buggy behavior when it comes to updating existing date values in the input that makes this method impossible. (the functionality works correctly in the JQuery version of the library, just not React)
When updating an existing value in the box from a single digit value (e.g. 01, 02, 03, 04, but not 10, 11, 12) instead of overwriting the existing value it appends the new number the user entered. For example, if a 01, is in the box and the user types 2 it becomes 12, when it should have become 02.
This can be especially confusing for the user when working with named dates (e.g. "Jan", "Feb", "Dec", etc) since they do not see the numbers involved. If the user is updating Jan, and they press 2. It should update to Feb not Dec...
I've attached a GIF of the problem below as I've described
Environment (OS, Application, Versions):
OS Version: 22H2 (OS Build 25352.1)
Edge Dev: Version 121.0.2277.112 (Official build) (64-bit)
Repro Steps:
1. Open https://codepen.io/oneID/pen/LYaGREP and turn on NVDA.
2.Navigate to Populate grid and activate it using enter key.
3.Navigate to Expand button under domain in export to excel table.
4.Verify if the accessible name and role for the expand button is correct or not.
Actual Results:
Accessible name for the 'expand' button is not correct, Expand button is defined as link.
Expected Results:
Accessible name of 'expand' button should be sufficient for screen reader user. Accessible name should contain value available in domain as well.
Role should be defined as 'Button' as its behaving as button.
Users with low vision who rely on high contrast will not be able to distinguish between the checked and unchecked checkboxes in high contrast Aquatic/Desert themes.
This is a bug on your documentation website.
Go to https://www.telerik.com/kendo-react-ui/components/grid/ for example to see that the side panel on the left is empty in an Edge browser. It flickers then it disappears.
It works fin in Chrome and Firefox.
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!
Attempting to select a comboBox value with a down arrow key press when there is only a single item in array results in a crash.
I'm adding a link to a modified version of combobox demo showcasing the error.
Steps for reproduction:
Title basically says it all. Issue can be easily observed in the basic Multiselect with virtualization example:
What seems strange is that I cannot reproduce this issue with the combobox virtualization, although I found a somewhat similar bug submitted for the combobox - https://github.com/telerik/kendo-react/issues/1450