Declined
Last Updated: 13 Mar 2025 09:38 by ADMIN

@progress/kendo-react-inputs@9.0.0

going back to this ticket, we'd like to use CTRL+up/down for our own purposes... as such, you can now disregard that feature request in lieu of fixing this bug =)

since this is undocumented behavior (documentation screenshot below) i believe we have a legitimate bug claim.

also, other controls like DateTimePicker reliably ignore the CTRL+up/down while implementing bare up/down as documented.

 

Unplanned
Last Updated: 19 Dec 2024 15:44 by ADMIN
Created by: JeffSM
Comments: 1
Category: KendoReact
Type: Feature Request
0
Please would be great a control to read QRCode.
Completed
Last Updated: 23 Jan 2025 18:20 by ADMIN
Created by: Brent
Comments: 2
Category: KendoReact
Type: Bug Report
0

here's a simple repro project minimally tweaked from an original kendo demo:

https://codesandbox.io/p/sandbox/suspicious-lovelace-8nmzgj?file=%2Fpackage.json

just start dragging a column resize handle and you should see the "jitter" right away. in our experience, the jitter is so pronounced that resizing columns is no longer practically usable.

please note this bug is definitely related to putting the kendo grid inside of a css-grid, see that definition in the parent <div style>

as you may imagine, we use css-grid for our overall page layout which i believe is still modern best practice and we really hope you can fix this regression within that usage context.

note, the bug manifests regardless of the gridTemplateAreas or gridTemplateColumns, you can eliminate those entirely and it's still present.

hopefully helpful for tracking down:  it appears this started exactly in version "@progress/kendo-react-grid": "9.0.0-develop.11"... notice if you change back to @progress/kendo-react-grid v9.0.0-develop.10 the columns will no longer jitter upon resize.
 
gif video attached just to be sure the issue is clear
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:

Unplanned
Last Updated: 19 Feb 2025 12:59 by ADMIN
Created by: Mahesh
Comments: 1
Category: KendoReact
Type: Feature Request
0

Hi Team,

I am writing to inquire about modifying the default behaviour of the Kendo UI Menu component. The sub-menu items are displayed when hovering over the parent menu item. However, I require the sub-menu items to be visible only when the parent menu item is clicked.

Desired Behavior:

Sub-menu items should remain hidden by default.
Clicking on the parent menu item should expand the sub-menu and display the child items.
Clicking on another parent menu item should collapse the previously expanded sub-menu and expand the new one.
Implementation Challenges:

I have explored the Kendo UI documentation and API, but I am unable to find a direct configuration option to achieve this desired behaviour.

Could you please provide guidance on how to modify the Kendo UI Menu component to display sub-menu items only on click of the parent menu item?

Please let me know if you require any further information or if there are any examples available that demonstrate this functionality.

Reference URL - https://stackblitz.com/edit/react-zugkrezk?file=app%2Fapp.jsx,app%2Fapp.css 
Reference Ticket - https://www.telerik.com/account/support-center/view-ticket/1679073 

Thank you for your time and assistance.
Mahesh

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: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.

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'.
    Duplicated
    Last Updated: 27 Feb 2025 11:31 by ADMIN

    Drag-and-Drop editing is a very usefull and required functionality in a lot of enterprise apps (Move/resize tasks along the timeline, adjust completion percentage, dependencies editing).
    We noticed these features are (maybe partially) available in the Kendo Gantt components for (at least) jQuery and Angular.
    Are there plans to introduce similar functionality in the KendoReact Gantt component? If so, could you share a timeline for implementation? Or maybe you can suggest some workarounds? 

    We’d greatly appreciate your insights on this point, as it's critical to our evaluation process.

    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: 09 Apr 2025 08:25 by ADMIN
    Created by: Revanth
    Comments: 1
    Category: KendoReact
    Type: Feature Request
    0

    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

    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: 14 Apr 2025 12:37 by ADMIN
    Scheduled for Q2 2025 (May)
    Created by: Speedy
    Comments: 1
    Category: KendoReact
    Type: Bug Report
    0
    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. 
    Unplanned
    Last Updated: 17 Apr 2025 08:20 by ADMIN

    It is not possible to set default values for the column menu filter.  Applying a default filtering to the grid could not affect the column menu.


    const initialFilter = {
      logic: "and",
      filters: [
        {
          field: "name",
          operator: "contains",
          value: "bu",
        },
      ],
    };
    I want to see values and operators of initial filtering in column menu.

     

    Need More Info
    Last Updated: 05 May 2025 08:57 by ADMIN
    Created by: abdu bukres
    Comments: 1
    Category: KendoReact
    Type: Bug Report
    0
    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.

    Unplanned
    Last Updated: 18 Jun 2025 07:09 by ADMIN
    Created by: Hanoch
    Comments: 1
    Category: KendoReact
    Type: Feature Request
    0

    Hi,

    Add this feature.