Unplanned
Last Updated: 09 Apr 2025 07:43 by ADMIN
Created by: Carey
Comments: 1
Category: KendoReact
Type: Feature Request
0

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

Unplanned
Last Updated: 08 Apr 2025 13:07 by ADMIN
Created by: Huw
Comments: 2
Category: KendoReact
Type: Feature Request
2
Add an option to select multiple items in the DropDownTree with checkboxes.

This has to be similar to what we have in Kendo UI for jQuery:

https://demos.telerik.com/kendo-ui/dropdowntree/checkboxes
Completed
Last Updated: 03 Apr 2025 15:57 by ADMIN

in latest v9.3.1 it appears GridFilterCell isn't passing properties shaped as 'isRequired' on DatePicker popupSettings 

this does seem to be a regression because i just recently noticed it in latest upgrade which we need for other bug fixes.

i pursued patching myself by populating animate in GridFilterCell.mjs which seemed to work but then i got warning for the next required property "appendTo". however, populating appendTo yields warning "Warning: Failed prop type: Invalid prop `appendTo` supplied to `Kendo React Popup`. Validation failed." so it's not easily reconcilable that way... therefore i tried removing isRequired on all 3 DatePicker popupSettings properties which of course avoided warnings and i didn't see any negative side effects.

here is a codesandbox repro minimally tweaked to include a date field from kendo grid's "getting started" demo: https://codesandbox.io/p/sandbox/cool-sanne-d4tp85

admittedly this is just a warning but it does create unnecessary noise in browser debug which detracts from issues truly requiring attention during development.

screenshot with the warning from that demo repro:

Completed
Last Updated: 03 Apr 2025 15:52 by ADMIN
When I change the width of the component, I expect that the state of the buttons (active/locked) will change depending on the scroll position, but this does not happen. For example, if the component did not scroll and both buttons are locked, then when the width is reduced, they will also remain locked. I think this is a mistake. Is there a way around this problem?
Unplanned
Last Updated: 02 Apr 2025 15:20 by ADMIN

Hi,

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

Thank you.

Regards.

 

Unplanned
Last Updated: 31 Mar 2025 14:14 by ADMIN
Created by: Paxcom
Comments: 2
Category: KendoReact
Type: Feature Request
3

in the provided video, an example of the unordered list has been taken up. But the same is applicable to the numbered list as well.

When a user tries to add a new point to an unordered list in a new line and then clicks the backspace, the unordered list remains. Pressing 'Enter' to start a new line shows the unordered list bullet points again.

Can we update it so that on   Pressing backspace to remove the unordered/ordered list should delete it entirely and should not leave any highlighting in the description box editor field.

 

video : https://www.loom.com/share/480debbe4f2648339ecb80cd9b6ed853?sid=3914f5dc-f477-4afd-a55d-df4a26603da7   

please go through video where i have provided , example of current behavior and expected behavior 

Declined
Last Updated: 31 Mar 2025 14:10 by ADMIN
Created by: eDAD
Comments: 2
Category: KendoReact
Type: Bug Report
0

Test Environment:

OS: Windows_11
Version: 21H2
OS Build: 22000.795
Browser: Version 103.0.1264.71 (Official Build) (64-bit)

URL: https://agentcalendardevone.azurewebsites.net/SMBEntryForm.aspx?trg=testteam&campaign=Microsoft%20Internal%20Test%20Camapign

Screen Reader: NVDA (2021.3)

Repro Steps:

1. Open URL: SMB Scheduler (agentcalendardevone.azurewebsites.net) page in Edge Browser.

2. Provide valid 'Email address' in text field and activate 'Book New Appointment'.
3. Click on view Available Appointments.
4. Open NVDA.
5.Navigate and activate 'Calendar' icon where popup appears.
6.Naviagte to controls.

7. Observe an issue that Incorrect role 'link' is defined on button controls.

Actual Behavior:

Incorrect role 'link' is defined on button controls present on 'Calendar' popup.

Expected Behavior:

In this case, the expected role is {button}. All components need a proper role attribute, ideally with semantics. In rare cases a role attribute should be added to give full context and information to assistive technology. Learn more by reading about when to use an aria role and the html/aria role mappings.


Declined
Last Updated: 31 Mar 2025 14:09 by ADMIN
Created by: eDAD
Comments: 5
Category: KendoReact
Type: Bug Report
0

Environment Details:
OS: Windows11 version 21H2 (OS build 22000.856)
Edge Browser version: 
104.0.1293.47

Repro steps:
1. Open Code Pen: https://codepen.io/m1mrt/pen/VwXjEzJ page in Edge Browser.2. Run Axe dev tools3. Observe an issue that select element has an accessible name.

Actual Result:Select element does not have an accessible name.

Expected Result:
All components need an accessible name, ideally using semantic elements and attributes. In rare cases, aria-label or aria-labelled by may be needed to alter the name.

Screenshot attachment:

Declined
Last Updated: 31 Mar 2025 14:08 by ADMIN
Created by: Rodrigo
Comments: 2
Category: KendoReact
Type: Feature Request
0

We have problems with the grid because for no reason a 'display:none' appears, specifically in this creation action

We can't understand when the error might occur, we think it's a coincidence of class names.

Can you guide us through this error?

It is my first time raising a support contact so I don't know what background they can mostly support.

Greetings and thank you very much

imagen

Declined
Last Updated: 31 Mar 2025 14:08 by ADMIN

Actual Result:

While navigating in table, Narrator is not announcing as 'enter table' and it is also not announcing rows and column information. while navigating in table, With arrow keys or table navigation keys or tab key, Narrator is announcing as 'end of line/blank'.

With caps-arrow keys, Narrator is giving row and column information.

 

Expected 
While navigating in table, Narrator should announce as enter table and it should also give row and column information. And while navigating with arrow keys or table navigation keys or tab key, Narrator should not announce as 'end of line/blank' instead it should give row or column information


User Impact 
Visually impaired users who rely on screen reader will face difficulties to determining Row/Column information of a cell.
Completed
Last Updated: 31 Mar 2025 14:07 by ADMIN
Created by: Michael
Comments: 2
Category: KendoReact
Type: Bug Report
0
Hi thanks. When resizing a column the page skips in Edge. Please see attached video. KendoReact.
Completed
Last Updated: 31 Mar 2025 14:06 by ADMIN
Created by: lavanya
Comments: 2
Category: KendoReact
Type: Feature Request
0

I have attached files, in which there is an app bar content there is a dropdown in the dropdown there are four elements, in that I need four drawer container on the left side as I attached by clicking the single dropdown, how can I attach 4 drawer container in a single project 

 

Thank you

Declined
Last Updated: 31 Mar 2025 14:04 by ADMIN
Title: Screen reader is not announcing the search result information on giving invalid data in the search edit field in windows.

Test Environment: 
OS: Windows 11 Enterprise Insider Preview Version 24H2(OS Build 26100.2892)
Browser: Microsoft Edge Version 132.0.2957.140, Chrome Version 133.0.6943.54
Screen readers: NVDA (2024.4.2), JAWS (Version 2025.2412.50) and Narrator.

User Impact:
The absence of screen reader announcements for invalid search results affects users with visual impairments, including blind and low-vision individuals, as well as users with cognitive disabilities who depend on auditory feedback to understand and correct errors, limiting their ability to use the search functionality independently.

Observation: 
  1. This issue is observed with all three screen readers.
  2. Same issue is observed in chrome browser as well.
Pre-Requisite:
    1. Turn on Screen Readers:
      1. Narrator: Win + Shift + Enter
      2. NVDA: Ctrl + Alt + N
      3. JAWS: Ctrl + Alt + J
    2. Verbosity:
      1. Narrator: Default
      2. JAWS: Beginner, Highest
      3. NVDA: Default
Repro steps:
  1. Open the URL: Agora Home Page (PPE) in latest edge browser.
  2. Press tab key to move to the 'Save as' control present in the page and activate it using enter key.
  3. Save as dialog gets displayed.
  4. Press tab key to move to the 'workspace to be saved as in' edit field and activate it using 'Alt + down arrow key'.
  5. Enter any invalid data in the search edit field.
  6. Now Verify whether screen reader is announcing the search result information on giving invalid data in the search edit field in windows or not.
Actual result:
Screen reader is not announcing the search result information on giving invalid data in the search edit field in windows. Screen reader is remaining silent after giving invalid data in the edit field.
Observation: Screen reader is narrating the displayed result information on giving valid data in the edit field.

Refer Attachment: 
Screen reader is not announcing the search result information on giving invalid data in the search edit field in windows..wmv

Expected result:
Screen reader should announce the displayed search result information on giving invalid data in the search edit field in windows. Screen reader should narrate as "No data found'.
Declined
Last Updated: 31 Mar 2025 14:03 by ADMIN
Title: Screen reader is announcing incorrect name for the radio buttons present in the filter dropdown in windows.

Test Environment: 
OS: Windows 11 Enterprise Insider Preview Version 24H2(OS Build 26100.2892)
Browser: Microsoft Edge Version 132.0.2957.140, Chrome Version 133.0.6943.54
Screen readers: NVDA (2024.4.2), JAWS (Version 2025.2412.50) and Narrator.

User Impact:
 
This issue impacts visually impaired users who depend on screen readers to navigate the website, as the incorrect announcement of filter options may prevent them from selecting the right choices, hindering their ability to interact with the dropdown.

Observation: 
  1. This issue is observed with all three screen readers.
  2. Same issue is observed in chrome browser as well.
  3. Name is not properly defined for once control. Screen reader is narrating the name twice for the once control as "Once check box not checked report frequency: once"
    Path: Home > Header > Reports > Schedule a report button > Schedule a Report pop-up.
    Refer Attachment: Name is not properly defined for once control.png
Pre-Requisite:
    1. Turn on Screen Readers:
      1. Narrator: Win + Shift + Enter
      2. NVDA: Ctrl + Alt + N
      3. JAWS: Ctrl + Alt + J
    2. Verbosity:
      1. Narrator: Default
      2. JAWS: Beginner, Highest
      3. NVDA: Default
Repro steps:
  1. Open the URL: Agora Home Page (PPE) in latest edge browser.
  2. Press tab key to move to the 'Alerts' control present in the page and activate it using enter key.
  3. 'Alert Definitions' page gets displayed.
  4. Press tab key to move to the 'Functions? Filter' control and activate it using 'Enter key'.
  5. Navigate through the radio buttons in the displayed popup using arrow keys and verify whether screen reader is announcing incorrect name for the radio buttons present in the filter dropdown in windows or not.
Actual result:
Screen reader is announcing incorrect name for the radio buttons present in the filter dropdown in windows. Screen reader is announcing as "Function? Filter radio button checked 1 of 2"

Refer Attachment: Screen reader is announcing incorrect name for the radio buttons present in the filter dropdown in windows..wmv

Expected result:
Screen reader should announce correct name for the radio buttons present in the filter dropdown in windows. Screen reader should announce as "Is true radio button checked 1 of 2"

Declined
Last Updated: 31 Mar 2025 14:03 by ADMIN
Title: Visually appearing heading text 'Create Dashboard' in the dialog is not programmatically defined as heading.

Test Environment:
 
OS: Windows 11 Enterprise Insider Preview Version 24H2(OS Build 26100.2892)
Browser: Microsoft Edge Version 132.0.2957.140, Chrome Version 133.0.6943.54
Tools: F12 Developer Tools /Accessibility insights for web.

User Impact:
 
 
The lack of programmatic heading for the visually displayed "Create Dashboard" in the dialog affects blind and low-vision users who rely on screen readers to navigate and quickly locate key sections. It also impacts users with cognitive disabilities, who depend on well-structured headings for easier understanding and navigation.

Observation:
 
  1. Same issue repro on heading 'Workspaces & Dashboards' [appears on Home --> Header--> Hamburger menu--> Popup] (Refer Attachment: Note_1_Same issue repro on heading 'Workspaces & Dashboards'..mp4).
  2. Heading hierarchy is not sequential in the Home page.
Pre-Requisites:
  1. Turn on Accessibility insights for web extension.
  2. Navigate to the headings toggle control and turn it on.

Repro Steps:
  1. Open the URL: Agora Home Page (PPE) in latest edge browser.
  2. 'Agora home page (PPE)' will be displayed.
  3. Navigate to 'Hamburger' menu control using tab key and activate it using enter key.
  4. 'Workspace and dashboards' popup will be displayed.
  5. Navigate to 'Add dashboard' control in the list displayed using tab key and activate it using enter key.
  6. 'Create Dashboard' dialog gets displayed.
  7. Observe and verify whether visually appearing heading text 'Create Dashboard' in the dialog is not programmatically defined as heading or not.

Actual Result:
 
Visually appearing heading text 'Create Dashboard' in the dialog is not programmatically defined as heading.

Refer Attachment: 

Expected Result:
 
 
 
Visually appearing heading text 'Create Dashboard' in the dialog should be programmatically defined as heading level 2.
Ensure that heading structure should be logical in the page i.e., it should follow h1->h2->h3->h4->h5->h6.

Won't Fix
Last Updated: 31 Mar 2025 14:02 by ADMIN
 Title: Incorrect role as link is defined for the 'Filter' button in Windows.

Test Environment: 
OS: Windows 11 Version 24H2(OS Build 26100.2161)
Browser: Edge Version 131.0.2903.112 (Official build) (64-bit)
Screen Readers: Narrator, NVDA Version 2024.4.1, JAWS 2025.2412.50
    User Impact:
    Screen Readers users will not be able to understand the purpose of the control if Screen Reader is announcing incorrect role for the Filter button in Windows.

    Observation:
    1. This issue is observed with (NVDA, JAWS and Narrator) using down arrow key/Tab key.
    Pre-Requisite:
    1. Press F12 key to open the developer tool and inspect the code.
    Repro Steps:
    1. Open URL: https://demos.telerik.com/kendo-ui/grid/filter-menu-customization in Edge browser.
    2. Navigate to the Filter icon present in the city/Title/Birth date column header.
    3. Press F12 to open Dev tool and inspect the code for Filter button.
    4. Observe whether correct role is defined for "Filter" button or not.
    Actual Result:
    Incorrect role as link is defined for the 'Filter' button.

    Observation: 
    Keyboard focus is not moving to the filter icon. 
    Screen reader is announcing as 'Link city filter column settings'.

    Attachment Name: Incorrect role as link is defined for the 'Filter' button in Windows..mkv

    Expected Result:
    Correct role as 'Button' should be defined for the Filter button.
    Keyboard focus should move to the Filter button and Screen reader should announce as 'City Filter button column settings'.
    Won't Fix
    Last Updated: 31 Mar 2025 14:01 by ADMIN
    Title: Visually appearing heading text 'Create Text Widget' is not programmatically defined as heading.

    Test Environment:
     
    OS: Windows 11 Enterprise Insider Preview Version 24H2(OS Build 26100.2892)
    Browser: Microsoft Edge Version 132.0.2957.140, Chrome Version 133.0.6943.54
    Tools: F12 Developer Tools /Accessibility insights for web.

    User Impact:
     
    The absence of a programmatic heading for the visually displayed "Create Text Widget" impacts blind and low-vision users who rely on screen readers to quickly identify and navigate to key sections. It also affects users with cognitive disabilities, who depend on clear, structured headings for better understanding and easier navigation.

    Observation:
    1. Same issue is observed for the below two dialogs.
      1. Visually appearing heading 'Import Workspace' is not defined as heading programmatically. [Path: Home page-->activate 'Hamburger' menu-->Import workspace--> Popup] (Refer Attachment: Note_1_Visually appearing heading 'Create Workspace' is not defined as heading.png.)
      2. Visually appearing heading 'Create Workspace' is not defined as heading programmatically. [Path: Home page-->activate 'Hamburger' menu-->Add new workspace--> Popup] (Refer Attachment: Note_2_Visually appearing heading 'Import Workspace' is not defined as heading.mp4).
    Pre-Requisites:
    1. Turn on Accessibility insights for web extension.
    2. Navigate to the headings toggle control and turn it on.

    Repro Steps:
    1. Open the URL: Agora Home Page (PPE) in latest edge browser.
    2. 'Agora home page (PPE)' will be displayed.
    3. Navigate to 'Add a widget' control using tab key and activate it using enter key.
    4. Navigate to 'Mark down' control in the list displayed using tab key and activate it using enter key.
    5. 'Create text widget' dialog gets displayed.
    6. Observe and verify whether visually appearing heading text 'Create Text Widget' is programmatically defined as heading or not.

    Actual Result:
     
    Visually appearing heading text 'Create Text Widget' is not programmatically defined as heading.

    Refer Attachment: 
    Visually appearing heading text 'Create Text Widget' is not programmatically defined as heading..wmv

    Expected Result:
     
     
    Visually appearing heading text 'Create Text Widget' should be programmatically defined as heading level 2.
    Ensure that heading structure should be logical in the page i.e., it should follow h1->h2->h3->h4->h5->h6.

    Completed
    Last Updated: 31 Mar 2025 13:19 by ADMIN

     

    Environment (OS, Application, Versions)

    Repro Steps

    1. Open URL: Column Menu - Kendo React (telerik.com)
    2. Navigate to context menu controls available on column headers of Basic usage table.
    3. Verify if context menu is accessible using keyboard.

     

    Actual Results

    The 'context menu' controls available on the column headers under the basic usage table are not accessible using the keyboard.

     

    Expected Results

    The 'context menu' controls available on the column headers under the basic usage table should be accessible using the keyboard.

     

    Unplanned
    Last Updated: 31 Mar 2025 13:15 by ADMIN
    Created by: Alex
    Comments: 1
    Category: KendoReact
    Type: Bug Report
    0

    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.

     

    Completed
    Last Updated: 31 Mar 2025 13:00 by ADMIN
    Created by: Joel Parker Henderson
    Comments: 4
    Category: KendoReact
    Type: Bug Report
    0
    ## Missing kendo-react-popup

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

    On this section: "Add a KendoReact Data Grid"

    When I launch the app as usual:

    ```sh
    yarn start
    ```

    Then the browser page includes this error:

    ```
    Compiled with problems:

    ERROR in ./.yarn/__virtual__/@progress-kendo-react-data-tools-virtual-df92d36fcf/0/cache/@progress-kendo-react-data-tools-npm-5.2.0-8d098f65a0-5d68752aaa.zip/node_modules/@progress/kendo-react-data-tools/dist/es/columnmenu/ColumnMenuFilterForm.js 19:0-55

    Module not found: Error: @progress/kendo-react-data-tools tried to access @progress/kendo-react-buttons (a peer dependency) but it isn't provided by your application; this makes the require call ambiguous and unsound.

    Required package: @progress/kendo-react-buttons
    Required by: @progress/kendo-react-data-tools@virtual:79c9c696d5f1e6f4dd730946c0d2912611551a498926b146bcbdd9d142588c5f4c2333469b63e7a9a2bdd1f0f1313d0d70b72cc8dbcafcc20e21e6b9790f6068#npm:5.2.0 (via /Users/joel/git/joelparkerhenderson/demo/demo-react-kendo/.yarn/__virtual__/@progress-kendo-react-data-tools-virtual-df92d36fcf/0/cache/@progress-kendo-react-data-tools-npm-5.2.0-8d098f65a0-5d68752aaa.zip/node_modules/@progress/kendo-react-data-tools/dist/es/columnmenu/)
    Ancestor breaking the chain: demo-react-kendo@workspace:.



    ```

    The solution that works for me...

    Add the package:

    ```sh
    yarn add @progress/kendo-react-popup
    ````

    Edit `src/App.js` and add this line:

    ```js
    import '@progress/kendo-react-popup';
    ```