Pending Review
Last Updated: 20 May 2024 13:58 by Marcu
Created by: Marcu
Comments: 0
Category: KendoReact
Type: Bug Report
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:

  1. Scroll down within the grid.
  2. Click on any header cell multiple times.
  3. Scroll back to the top of the grid.

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.

Unplanned
Last Updated: 11 Apr 2024 11:10 by ADMIN
Repro-Steps:
  1. open the given URL using valid credentials.
  2. Navigate to 'Reply' button and invoke it.
  3. Navigate to 'table' button and invoke it.
  4. Now, try to navigate to table cells to select the size of the table and observe

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. 

Planned
Last Updated: 03 Apr 2024 07:28 by ADMIN
Created by: Owen
Comments: 3
Category: KendoReact
Type: Bug Report
2

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:

Unplanned
Last Updated: 25 Mar 2024 17:43 by ADMIN
Created by: Owen
Comments: 6
Category: DatePicker
Type: Bug Report
3

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

Duplicated
Last Updated: 29 Feb 2024 17:14 by ADMIN
Created by: eDAD
Comments: 0
Category: KendoReact
Type: Bug Report
0

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.

Completed
Last Updated: 15 Feb 2024 09:39 by ADMIN
Test Environment:
OS version: 22H2 (OS Build 25272. 1000)
Edge Dev Version: Version 111.0.1633.0 (Official build) dev (64-bit)

Pre- requisites: 
Open Settings -> Accessibility -> Contrast Themes -> Select Aquatic/Desert modes.

Repro-Steps:
  1. Open the above URL and login with valid credentials.
  2. Now check some checkboxes (e.g., Bold, Underline, Insert ordered list, etc.)
  3. Now apply high contrast themes and try to differentiate between the checked and unchecked checkboxes. 


Actual Result:

Unable to distinguish between the checked and unchecked checkboxes in high contrast Aquatic/Desert themes.

Expected Result:
User should be able to distinguish between the checked and unchecked checkboxes in high contrast themes also. 

User Impact:

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.

    Completed
    Last Updated: 01 Feb 2024 15:48 by ADMIN

    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

    Planned
    Last Updated: 25 Jan 2024 13:09 by ADMIN
    Created by: Kavitha
    Comments: 3
    Category: Editor
    Type: Bug Report
    0
    Repro-Steps:
    1. open answers.microsoft.com/en-us/msoffice/ using valid credentials.
    2. Navigate to any article link and hit enter.
    3. Select 'reply' button.
    4. Navigate to 'format' list and invoke it.
    5. Now Run the fast pass using Accessibility Insights for web and observe the failure 'aria input field name'.

    Actual Result:
    Aria input field doesn’t have an accessible name.

    Control type is defined incorrectly as list item for combo box for 'format' combo box.

    Expected Result:
    Ensure every aria input field should have an accessible name.
    Control type should be defined as combo box.

    User Impact:
    ARIA widget roles require additional attributes that describe the state of the widget. If a required attribute is not provided, the state of the widget will not be communicated to screen reader users.
    Completed
    Last Updated: 22 Dec 2023 15:28 by ADMIN
    Release [R1 2024] PI 2
    Created by: Jason
    Comments: 1
    Category: MultiViewCalendar
    Type: Bug Report
    1
    MultiViewCalendar component is broken in your library and in your example pages of it on your website at https://www.telerik.com/kendo-react-ui/components/dateinputs/multiviewcalendar/. Clicking the date label in the top left of the control is supposed to change the view level correctly but it does not, it seems to be a click behind in its behavior.

    To reproduce on your site at https://www.telerik.com/kendo-react-ui/components/dateinputs/multiviewcalendar/

    Click on this month label


    Then click any other month than the one you were in


    Then it shows the wrong (previous) month


    If you keep clicking up and down from here you will find it seems to be navigating to your previous click each time, not the current click. Please correct this as its a bug in my new application going to production soon.

    Thanks.
    Under Review
    Last Updated: 13 Dec 2023 09:07 by ADMIN

    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!

    Planned
    Last Updated: 29 Nov 2023 06:23 by ADMIN
    Created by: Simonas
    Comments: 1
    Category: ComboBox
    Type: Bug Report
    0

    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:

    1. Select comboBox field
    2. Click arrow key down to select first and only entry in the comboBox
    Under Review
    Last Updated: 16 Oct 2023 07:53 by ADMIN
    Created by: Grant
    Comments: 4
    Category: KendoReact
    Type: Bug Report
    0

    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

    In Development
    Last Updated: 14 Sep 2023 07:29 by ADMIN

    Title basically says it all. Issue can be easily observed in the basic Multiselect with virtualization example:

    1. Open the dropdown
    2. Scroll to the bottom end
    3. Close the dropdown
    4. Open it again - popup's scroll position is incorrect and therefore shows blank.

    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 

    Completed
    Last Updated: 05 Sep 2023 14:17 by ADMIN

    As per the subject, you can no longer use the Calendar to select a date in a month before the currently selected Date. Please see the following demo:

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

    Steps to reproduce:

    • Click on the Calendar button
    • Click on any month before the currently selected month
    • Click on any date in the month
    • Observe that the day is changed correctly but the month is incorrectly incremented by one

    This error is not observed if you:

    • type in a date
    • use the mousewheel to scroll to the earlier date instead of clicking on the month
    • use Firefox instead of Chrome

    We aren't certain but don't believe this error was present before the latest Chrome 113 update. The error is reproducible in all versions of KendoReact from 5.2.0 onwards.

    Completed
    Last Updated: 31 Jul 2023 07:16 by Joel Parker Henderson
    Created by: Joel Parker Henderson
    Comments: 4
    Category: KendoReact
    Type: Bug Report
    0

    On this page: https://www.telerik.com/kendo-react-ui/getting-started/

    There's a syntax mismatch in end-of-line semicolons.

    This line ends with a semicolon:

    ```js
    import '@progress/kendo-theme-default/dist/all.css';
    ```

    This line does not end with a semicolon:

    ```js
    import { Calendar } from '@progress/kendo-react-dateinputs'
    ```

    All teams that I know of consider it to be an error to do both ways in the same file.

    The solution is to pick one way then be consistent. The broader solution is to use a linter, such as ESLint, that can process the code to ensure you're using your expected syntax and formatting.

     

    Completed
    Last Updated: 30 Jul 2023 05:57 by ADMIN
    I've already submitted this to the GitHub issues - https://github.com/telerik/kendo-react/issues/1297

    Submitting here as it is an important regression with React 18 breaking all popup animations.
    Completed
    Last Updated: 30 Jul 2023 05:51 by ADMIN

    According to https://www.telerik.com/kendo-react-ui/components/installation/source-code/#toc-source-repository the repo should be updated nightly. However it does not seem to be.


    ~/Projects/kendo-react-private (master) git remote -v origin https://kendo.git.progress.com/kendo-react-private.git (fetch) origin https://kendo.git.progress.com/kendo-react-private.git (push) ~/Projects/kendo-react-private (master) git fetch --tags ~/Projects/kendo-react-private (master) git pull origin master From https://kendo.git.progress.com/kendo-react-private * branch master -> FETCH_HEAD Already up to date. ~/Projects/kendo-react-private (master) git tag | grep v5 v5.0.0 v5.0.0-dev.202201182040

     

    ~/Projects/kendo-react-private (master) git log
    commit 4bf2535e414ba2f342ddbef8daac9ec052f04cc2 (HEAD -> master, tag: v5.0.0, origin/master, origin/HEAD)
    Author: kendo-bot <kendouiteam@progress.com>
    Date:   Tue Jan 18 22:41:34 2022 +0200

        chore(release): publish 5.0.0-dev.202201182040

    v5.0.0 seems to be the latest tag. Could someone verify that the github repo is actually being updated?

    Thanks for any help!

    Completed
    Last Updated: 30 Jul 2023 05:21 by ADMIN
    Created by: Rita
    Comments: 3
    Category: KendoReact
    Type: Bug Report
    0

    toODataString throw exception on text filter changed from is null to contains. 

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

    Repro step:

    1. Choose filter by Name which is using text filter.

    2. Change filter from Is null to contains.

    3. toODataString threw exception.

     

    Error in /turbo_modules/@progress/kendo-data-query@1.5.5/dist/cdn/main.js (1:7873)
    Cannot read properties of undefined (reading 'replace')
    Completed
    Last Updated: 30 Jul 2023 05:21 by ADMIN
    Completed
    Last Updated: 30 Jul 2023 05:18 by ADMIN
    Release 4.6.0
    AutoComplete focused item is not set correctly if the items are with different height.

    Currently, it is required to have the same height for the items, but this can be very hard in cases when the items are dynamic with various height.
    1 2 3 4 5 6