Example: https://runner.telerik.io/fullscreen/yypoqSea

This example is based on the example from the docs with `navigatable: true` and enough data that the user needs to scroll in order to see the bottom row.

On Chrome on macOS, the filter menu cannot be used when `navigatable: true` and "Tap to click" is enabled in the macOS Trackpad settings. When clicking on the filter icon, the menu disappears very quickly (see screen recording). As a workaround, setting `navigatable` to false seems to resolve the problem. The same issue does not seem to occur on Safari, however, there is still odd behavior with the scrolling.

For some reason, screen size, resolution, and window settings impact the ability to reproduce the issue. The most reliable way for me to reproduce the issue was with Chrome in full screen on a 16-inch MacBook (13-inch works too) with the bookmarks bar showing and no external displays connected. Hiding the bookmarks bar or not using full screen seems to make it more difficult to reproduce.

Bug report

When there are multiple Forms on the same page, submiting one of the Forms triggers the other Forms validation.

Reproduction of the problem

1. Open the Dojo - https://dojo.telerik.com/rkDeetHu
2. Click the 'Submit' button on the second Form.

Current behavior

The first Form is also validated and the field is marked as invalid.

Expected/desired behavior

Only the Form which button has been clicked have to be validated.

The issue is a regression starting with 2025.1.211 version

Environment

• Kendo UI version: 2025.1.211
• Browser: [all]

Enhancement

Expose setOptions() for Kendo Wizard

Desired Behavior
setOptions shall update Wizard steps

    wizard.setOptions({
      steps: steps
    });

Destroy current Wizard and reinitialize with new steps

    let wizard = $("#wizard").data('kendoWizard');
    wizard.destroy();
    $("#wizard").empty();
    
    let steps = [];
    for	(var i = 0; i < 4; i++) {
      steps.push({
        title: "Tab " + i,
		content: "Tab Content " + i 
      });
    }
    
    $("#wizard").kendoWizard({
        steps: steps
    });

Dojo: https://dojo.telerik.com/zpjBsSkN

Kendo UI core lists several controls that are available in the library, but there is no mention that they are not actively maintained on main repository readme.

Several controls were obsoleted/unsupported in this commit - https://github.com/telerik/kendo-ui-core/commit/db16f60ee6ee43506173a9628723b3de1ed73266, but they are still listed in https://github.com/telerik/kendo-ui-core/blob/master/README.md or promotional graphics.

Please clarify its current/future status.

Best regards

K

Bug report

In a Spreadsheet that has a scrollable Sheetbar, clicking the arrow icons to scroll the sheets refreshes the page.

Regression introduced with 2024.4.1112

Workaround - https://dojo.telerik.com/IVcuYtjD/5

Reproduction of the problem

1. Open this Dojo example - https://dojo.telerik.com/ZXBKGnNe
2. Click on the arrow buttons to scroll the sheets

Current behavior

The page refreshes

Expected behavior

The page shouldn't refresh

Environment

• Kendo UI version: 2025.1.227
• Browser: [all]

There are many properties that can be set during initialization that cannot be changed through the API afterwards.

Take the Kendo UI ToolBar for example. You can add a button to the toolbar and set the text, but you cannot change the text afterwards unless you update the element directly. It may seem like a simple thing to change the text of an element, like so: $("#myButton").text("New Text"). However, if you had set the imageUrl as well, setting the text like I did above would remove the image. Knowing that, you could get the text node and update the nodeValue. That may work today but could easily be broken during a Kendo UI update (for example, if the update included a change that wraps the text in a span).

Having to deal with native elements after they have been created by the Kendo UI components is a dangerous practice for developers as it requires an internal knowledge of how elements are rendered based on the different options set. As mentioned above, it is also dangerous as any update could break our code. Therefore, it is imperative to expose methods that allow us to modify any properties through the API (where possible) to allow us to create clean and easy to maintain code.

If you search the feedback, you will see many requests to add a method here and a method there. There is even a related one to this called "Kendo Mobile: Methods to set properties dynamically".

Suggestion: When you have child elements, such as buttons on the toolbar, please allow us to update those widgets directly rather than through the parent. For example, instead of $("#myToolbar").data("kendoToolBar").enable("#myButton"), allow us to do something like this $("#myButton").data("kendoToolBarItem").enable();

Bug report

In a scenario where a Validator is created with validateOnBlur:false, and is used to validate a NumericTextBox, if the component is focused and blurred after validation, the k-invalid class is removed.

Reproduction of the problem

1. Open this Dojo example - https://dojo.telerik.com/lJzoPddG/3
2. Click the button to validate the fields.
3. Focus and blur the NumericTextBox

Current behavior

The k-invalid class, and the styles associated with it, are removed

Expected behavior

Environment

• Kendo UI version: 2025.1.227
• Browser: [all]

there is no binding for noData

e.g.

        noData?: boolean | undefined;

    interface ChartOptions {
        name?: string | undefined;
        autoBind?: boolean | undefined;
        axisDefaults?: ChartAxisDefaults | undefined;
        categoryAxis?: ChartCategoryAxisItem | ChartCategoryAxisItem[] | undefined;
        chartArea?: ChartChartArea | undefined;
        dataSource?: any|any|kendo.data.DataSource | undefined;
        legend?: ChartLegend | undefined;
        panes?: ChartPane[] | undefined;
        pannable?: boolean | ChartPannable | undefined;
        pdf?: ChartPdf | undefined;
        persistSeriesVisibility?: boolean | undefined;
        plotArea?: ChartPlotArea | undefined;
        renderAs?: string | undefined;
        series?: ChartSeriesItem[] | undefined;
        seriesColors?: any;
        seriesDefaults?: ChartSeriesDefaults | undefined;
        theme?: string | undefined;
        subtitle?: string | ChartSubtitle | undefined;
        title?: string | ChartTitle | undefined;
        tooltip?: ChartTooltip | undefined;
        transitions?: boolean | undefined;
        valueAxis?: ChartValueAxisItem | ChartValueAxisItem[] | undefined;
        xAxis?: ChartXAxisItem | ChartXAxisItem[] | undefined;
        yAxis?: ChartYAxisItem | ChartYAxisItem[] | undefined;
        zoomable?: boolean | ChartZoomable | undefined;
        axisLabelClick?(e: ChartAxisLabelClickEvent): void;
        dataBound?(e: ChartDataBoundEvent): void;
        drag?(e: ChartDragEvent): void;
        dragEnd?(e: ChartDragEndEvent): void;
        dragStart?(e: ChartDragStartEvent): void;
        legendItemClick?(e: ChartLegendItemClickEvent): void;
        legendItemHover?(e: ChartLegendItemHoverEvent): void;
        legendItemLeave?(e: ChartLegendItemLeaveEvent): void;
        noteClick?(e: ChartNoteClickEvent): void;
        noteHover?(e: ChartNoteHoverEvent): void;
        noteLeave?(e: ChartNoteLeaveEvent): void;
        paneRender?(e: ChartPaneRenderEvent): void;
        plotAreaClick?(e: ChartPlotAreaClickEvent): void;
        plotAreaHover?(e: ChartPlotAreaHoverEvent): void;
        plotAreaLeave?(e: ChartPlotAreaLeaveEvent): void;
        render?(e: ChartRenderEvent): void;
        select?(e: ChartSelectEvent): void;
        selectEnd?(e: ChartSelectEndEvent): void;
        selectStart?(e: ChartSelectStartEvent): void;
        seriesClick?(e: ChartSeriesClickEvent): void;
        seriesHover?(e: ChartSeriesHoverEvent): void;
        seriesOver?(e: ChartSeriesOverEvent): void;
        seriesLeave?(e: ChartSeriesLeaveEvent): void;
        zoom?(e: ChartZoomEvent): void;
        zoomEnd?(e: ChartZoomEndEvent): void;
        zoomStart?(e: ChartZoomStartEvent): void;
    }

It will be really useful if we could include a new 'filtering mode' in which operators like 'and' or 'or' are allowed in the filtering input box.

For instance, using the "doesnotcontain" with 'march or july or september' will allow users to exclude multiple conditions in a single filter

Bug report

Scrollable menu opening wrong menu on mobile

Reproduction of the problem

This is reproducible in Chrome developer tools - using iPhone 14 Pro Max

Dojo: https://runner.telerik.io/fullscreen/jtDsGBpV

1. Scroll a little to the right to have Ladies partially hidden

2. Click on Ladies

3. Notice that the ladies is focused and scrolled to be fully visible but the opened submenu is Mens

Environment

jQuery: 3.4.1

Kendo UI version: 2025.1.227
Browser: [all]

Bug report

When there is a filter applied in Excel file and the file is imported in the Spreadsheet only the first row is visible. The issue occur when the filtered column is a numeric column.

Reproduction of the problem

1. Open the Demos - https://demos.telerik.com/kendo-ui/spreadsheet/index
2. Import the file

Book1.xlsx

Current behavior

Only the filter row is visible. The filter result data rows are hidden:

Expected/desired behavior

All rows with filtered results should be visible. Example:

The issue is a regression starting with 2024.4.1112 release

Environment

• Kendo UI version: 2025.1.227
• Browser: [all ]

Bug report

In the TimeDurationPicker, if the columns format is configured as ##, when the user types a value - the result will be incorrect.

Reproduction of the problem

1. Open this Dojo example - https://dojo.telerik.com/CmVDhocz/2
2. Try typing 11:11:11 in the input

Current behavior

Incorrect value in the input

Expected Behaviour

The value of the input should be 11:11:11

Environment

• Kendo UI version: 2025.1.227
• Browser: [all]

Enhancement

Expose autocomplete attribute for Kendo TextBox

Overview

Upon initializing the Kendo UI TextBox, the autocomplete attribute is initially set to off.

While this is suggested on MDN in most scenarios, there are use-cases where it is necessary to set autocomplete to new-password to avoid auto-filling.

Desired Behavior

Extend the API to allow setting the autocomplete attribute. This could be done in a similar way as the inputMode configuration.

Workaround

Use jQuery attr method to set the item in the Ready event

   $(function(){
     $('#textBox').attr('autocomplete', 'new-password');
   });

Bug report

Currently, if you focus the command buttons, pressing tab will navigate to the buttons on the next row.

Reproduction of the problem

1. Open this dojo example - https://dojo.telerik.com/lmIJIUCH/2
2. Click on the cell containing the command buttons on the first row
3. Press enter to focus the Edit button
4. Press tab multiple times.

Current behavior

The focus will move to the buttons on the next row.

Expected/desired behavior

When the focus is on the Delete button, pressing Tab should return the focus to the current cell so that you can navigate to the remaining cells on the same row.

Environment

• Kendo UI version: 2024.3.1015
• Browser: [all]

Bug report

Pie and Donut Chart can not be exported to PDF, Png or Jpg

Reproduction of the problem

1. Open the demos - https://demos.telerik.com/kendo-ui/pdf-export/index or the Dojo - https://dojo.telerik.com/LfDhdqXf
2. Try to export the Chart in any format

Current behavior

The pie and donut charts are missing.

Expected/desired behavior

The Charts should be exported to the selected file format

The issue is a regression starting with 2024.4.1112

Environment

• Kendo UI version: 2024.4.1112
• Browser: [all]

Steps to reproduce the problem:

Have a grid with:

• specified width (e.g: 1000)
• column virtualization
• multiple columns with a width of 100, but most of them hidden in initial state (e.g.: 50 total, but only 8 shown)
• columnMenu true
• resizable true
  

When running the code that create the grid, the initial state looks like this:

Current behavior:

The header columns are filling the width of the grid (each bigger than the specified 100), but the rows columns cells have the specified width of 100, causing a misalignment.

However, changing the width of a column with the resize handle fixes all the widths (header + rows). 
Same thing for adding/removing a column from the menu.

See the attached video for an example.

If in the initial state there are more shown columns so they can fill the grid width (and have the horizontal scrollbar), the issue is not present.

Expected behavior:

Rows columns should always match the width of the header.

Dojo example:

Here's an example, based on the one from https://demos.telerik.com/kendo-ui/grid/column-virtualization 

https://dojo.telerik.com/@pgarand/UfEkIGiD

Bug report

The icons for 'Move previous' and 'Move next' in the 'Set Column Position' ColumnMenu item in RTL Grid are not correct.

Reproduction of the problem

1. Open the Dojo example - https://dojo.telerik.com/arOKEreq
2. Open the column menu of a random column.
3. Expand the 'Set Column Position' item.

Current behavior

The previous and next icons do not correspond to the correct direction.

Expected/desired behavior

The positions of the previous and next icons should be switched.

Environment

• Kendo UI version: 2023.2.718
• Browser: [all]

Describe the bug
When the user selects a word and changes its style (for example bold, italic, etc.) the content of the inline Editor is wrapped on multiple lines.

To reproduce
Steps to reproduce the behavior:

1. Go to Dojo - https://dojo.telerik.com/JNAQLLsy
2. Select a word in the editor and change its style from the tools.

Expected behavior
The content should not wrap.

Screenshots

Workaround

<style>
      .k-editor{
        display: block
      }
</style>

Dojo - https://dojo.telerik.com/iZZPZIGg

Regression since 2022.1.119

Affected package (please remove the unneeded items)

• theme-default
• theme-bootstrap
• theme-material

Affected suites (please remove the unneeded items)

• Kendo UI for jQuery

Affected browsers (please remove the unneeded items)

• All

In my application, I have grids with dozens of hidden fields. 

It would be beneficial if I could filter the available columns similar to what's available in the Windows Forms column chooser: