Unplanned
Last Updated: 18 Jun 2025 17:07 by Zac

Hello,

My development team is working with a business that has a design requirement for each calendar in the MultiViewCalendar component to have its own month and year label.

From what I can tell by looking at the documentation for this component, the MultiViewCalendar does not support defining labels that can be placed above each individual calendar. It only supports showing a single label that is a range from the start month + start year to the end month + end year.

I attached a screenshot of how our current UI looks using this component.

In this example, we would love to be able to attach a label of March 2025, April 2025, May 2025, and June 2025 above each calendar, rather than only being able to show a label of March 2025 - June 2025 above the first calendar.

Please let me know if you have any questions or concerns regarding this request. Thanks for your time.

Best,

Tyler Earls

Unplanned
Last Updated: 05 Jun 2025 18:20 by Mesut
Created by: Mesut
Comments: 0
Category: KendoReact
Type: Feature Request
1
It would be beneficial if the MaskedTextBox and other relevant components had a rawData prop exposed as in Kendo Ui for Vue
Duplicated
Last Updated: 03 Jun 2025 14:51 by ADMIN
Created by: Emery
Comments: 0
Category: KendoReact
Type: Feature Request
1
It would be beneficial if the KendoReact Scheduler had a occurrencesInRange prop same
as https://www.telerik.com/kendo-jquery-ui/documentation/api/javascript/ui/scheduler/methods/occurrencesinrange
Unplanned
Last Updated: 06 May 2025 05:46 by ADMIN
Created by: Maria
Comments: 1
Category: KendoReact
Type: Feature Request
2

Hi,

I would like to put forward a feature request to allow the panel bar items to be mounted when the panel bar itself mounts, irrelevant of whether it has been opened or not.

I'm looking for something like the keepItemsMounted property https://www.telerik.com/kendo-react-ui/components/layout/panelbar/mounted-items, but without the condition that a panel bar has to be opened at least once for them to stay mounted.

 

Completed
Last Updated: 04 Nov 2025 12:58 by ADMIN
Created by: abdu bukres
Comments: 2
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: 01 May 2025 11:51 by ADMIN

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?

Unplanned
Last Updated: 17 Apr 2025 12:55 by Michelle
Created by: Michelle
Comments: 0
Category: KendoReact
Type: Feature Request
6

It would be beneficial if we could pass inline functions for the selectMessageUI. Observe in the following example that you cannot pass an inline function to selectMessageUi the same way you can for onBlur and onChange:

https://stackblitz.com/edit/react-1lvt8y8d

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.

 

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: 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: 20 May 2025 10:26 by ADMIN
Created by: Rebecca
Comments: 4
Category: KendoReact
Type: Feature Request
5
Add support for the Unstyled Mode to the KendoReact Grid.
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: 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 08:11 by ADMIN

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.

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: 27 Feb 2025 11:38 by ADMIN
Created by: Manjula
Comments: 1
Category: KendoReact
Type: Feature Request
4

Hi Team,

We are using data-grid along with excel export for showing lakhs of data (sometimes over 20 lakhs) in our app and over 80 columns.  We found a the TIME TAKEN is over 2.5 mins for over 10 lakhs (rows*cols) data. We have tried the KendoOmxml with kendo saveAs function from file-saver as well.

I have tried with server-side export instead of client-side aslo and still it's the same behavior. In my observation I am suspecting the below line. 


 component.toDataUrl().then((dataURL) => {

Here component is the reference of ExportExcel component. After getting dataURL I am calling save api to download the file. But toDataUrl() function is taking the whole time. Is there any way we can get this base64 dataURL faster?

 

You can refer to the codeSandbox Link. We have 80 columns(including duplicates), while importing productsSmall.json file which contains 77 rows, export excel is working well and good. But when you change the import to productsLarge.json file which contains 10,000 rows (if cannot be seen, please copy paste the dummy data from attached file with even more usual amount of data we use in our app), the screen is stuck or takes too much time to get process complete and sometimes it throws error(maybe because of codesandbox incapability).

Stackblitz link (if codesandbox hangs more) https://stackblitz.com/edit/react-q5wlpg-4bs2zc?file=app%2Fmain.tsx

We have a large number of customers requesting this feature to be fast. Please let us know with an optimized solution. 

Regards,

Manjula

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.

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.

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.

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"