### Bug report

When the Grid is initialized in a hidden container (for example, in a non-selected tab of a TabStrip) and its initial data binding is disabled (autoBind: false), the pager information is not visible when the data is loaded afterward.

### Reproduction of the problem

1. Initialize a Grid into a non-selected tab of a TabStrip and set its autoBind option to "false".

2. Select the tab and check how the empty Grid is rendered.

3. Call the read() method of the Grid's DataSource in the browser console to request the data.

4. The data is loaded, but the pager information remains hidden.

A Dojo sample for reproduction: https://dojo.telerik.com/njVgBvza

### Expected/desired behavior

The pager information must be available when the data is loaded into the Grid.

### Environment

* **Kendo UI version: 2024.4.1112
* **jQuery version: 3.7.1
* **Browser: [all]

### Bug report

When removing a data item through the DataSource remove() method, and then trying to add a new record in the Grid, the editable row does not close when clicking the "Save" command. The Grid is set up for InLine editing. 

### Reproduction of the problem

1) Create an InLine editable Grid that binds to local data.

2) Add a custom column command that removes the respective data item by using the remove() method of the DataSource.

3) Delete a specified Grid record through the custom command.

4) Add a new record and click the built-in "Save" command.

5) The row remains in edit mode.

A Dojo sample for reproduction: https://dojo.telerik.com/IQIDuGOt

The last working version is 2024.1.130

### Expected/desired behavior

The editable row must close when clicking "Save" or "Cancel".

### Workaround

Use the Grid removeRow() method rather than the DataSource remove() method.

### Environment

* **Kendo UI version: 2024.1.319
* **jQuery version: 3.7.0
* **Browser: [all]

Bug report

Reproduction of the problem

1. Open the Dojo - https://dojo.telerik.com/FcHfotEy
2. Hover over more than one image

Current behavior

Only the first image has the correct width and height

Expected/desired behavior

The Tooltip should respect the width and height size configurations.

Workaround:

contentLoad: function (e) {
              $(".k-tooltip.k-popup").width(500).height(500);
            },

https://dojo.telerik.com/lvXLxxYD 

TicketID: 1717434

The issue is a regression starting with 2026.2.520 version

Environment

• Kendo/Telerik version: 2026.2.520
• Browser: [all ]

Using the latest 2026.3.811 version produces the following errors:

• kendo.all.d.ts(12072,26): error TS2552: Build:Cannot find name 'SchedulerKendoKeydownEvent'. Did you mean 'SliderKendoKeydownEvent'?
• kendo.all.d.ts(14372,9): error TS2416: Build:Property 'options' in type 'ToggleButton' is not assignable to the same property in base type 'Button'.
• kendo.all.d.ts(14384,15): error TS2430: Build:Interface 'ToggleButtonOptions' incorrectly extends interface 'ButtonOptions'.

Bug report

Reproduction of the problem

1. Open the Dojo - https://dojo.telerik.com/zjwPGXDx/3
2. Click → Open Window 1 → Open Window 2 → Open Payroll Window
3. In the Add Payroll change a value and click Save

Current behavior

The Dialog is displayed below Kendo Widnow although the .open() method is used which should invoke .toFront()

Expected/desired behavior

As the Dialog is the last opened Dialog/Window it should be displayed over the Window

TicketID: 1717764

Workaround:

setTimeout(function(){              
              kdAddPayrollError.open();
            }, 500)

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

The issue is a regression starting with: 2025.4.1217

Environment

• Kendo/Telerik version:
• jQuery version: x.y
• Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

Bug report

The DateTimePicker's popup calendar view is cut in the Default, Classic, and Fluent themes.

Reproduction of the problem

1. Run the following dojo
2. Set the sizing option of the widget to large.
3. Open to DatePicker popup.

Current behavior

The Date and Time views in the DateTimePicker popup are trimmed.

Expected/desired behavior

The Date and Time views in the DateTimePicker popup should not be trimmed.

Environment

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

Bug report

When a user creates a filter with a date, it starts as an empty Datepicker, but the value is appearing as an empty string. Thus, if the user clicks apply, an error appears in the console. If you place a value in the DatePicker and clear it, the value will be Null.

Reproduction of the problem

1. Go to this Progress Telerik ASP.NET Core REPL.
2. Add filter for a Date but keep the datepicker empty.
3. Select apply.
4. Now, add a date and clear the value.

Current behavior

The filter menu sends isnull filter queries in the following format:

While the Filter component sends it as follows:

As a result the ToDataSourceResult method fails.

Expected/desired behavior

If the DatePicker is empty, the filter should properly perform the 'isnull' query upon clicking apply.

Environment

• Kendo UI version: 2023.2.606
• jQuery version: All Supported Versions
• Browser: all

### Bug report

On mobile devices, when the TaskBoard columns are filled with cards, the users have trouble scrolling horizontally through the columns. When they attempt to scroll the screen, they accidentally drag cards instead of scrolling the columns. This makes navigation in the TaskBoard quite difficult, particularly for projects with a large number of cards.

### Reproduction of the problem

1. Create a TaskBoard with at least two columns.

2. Fill the columns with cards.

3. Open the browser DevTools and switch to mobile view. Tap a card to scroll the columns horizontally or tap at the bottom of the TaskBoard to activate the horizontal scrollbar.

4. The last card is accidentally dragged.

A Dojo sample for reproduction: https://dojo.telerik.com/izASODan

### Expected/desired behavior

When the user makes a hold/long press/long tap, show the "indicator for drag and drop" and then he/she continues with the gesture by moving the card to the desired column and lift the finger. This way, the accidental dragging will be prevented. For more information, refer to the GitHub issue.

Note: The cards in the TileLayout can be dragged only through the card's title element. The TaskBoard cards can be dragged through the card's body, as well.

### Environment

* **Kendo UI version: 2024.3.806
* **jQuery version: 3.7.0
* **Browser: [all]

The FormItemBuilder exposes an EditorTemplateView method which allows a view to represent the item and provides the entire modal to the view.

As the elements available to forms are limited to those hard coded by Telerik and whilst extension methods can be employed to expand this limitation slightly, the ability to create a context specific view would be ideal

The current implementation looks like this

Html.Kendo().Form<Model>()
    .Items(items =>
    {
        items.AddGroup("Test", 1, 10)
            .Items(i =>
                {
                    i.Add().Field(x => x.Username)
                    i.Add().Field(x => x.Password).EditorTemplateView(Html.Partial("MyView"))
                }
            );
    })

In this example, the entire model is provided into MyView. 

I suggest adding an EditorTemplateFor that uses the lamda expression provided in the Field() method such as

Html.Kendo().Form<Model>()
    .Items(items =>
    {
        items.AddGroup("Test", 1, 10)
            .Items(i =>
                {
                    i.Add().Field(x => x.Username)
                    i.Add().Field(x => x.Password).EditorTemplateViewFor(Html.Partial("MyView"))
                }
            );
    })

Currently, the DatePicker can be set to read-only mode by adding the "readonly" attribute through the HtmlAttributes() option or by calling the client-side readonly() method.

Is it possible to implement a built-in Readonly() option, so the DatePicker is initialized as read-only? For example:

@(Html.Kendo().DatePickerFor(m => m.StratDate)
  .Readonly(true)
)

### Bug report

When adding custom classes or styles to the TimeDurationPicker component, they are applied to the hidden input elenent rather than to the parent element.

### Reproduction of the problem

1. Create a TimeDurationPicker and add a class to its element:

<input id="timedurationpicker" class="testClass" />

2. When you inspect the component's markup, the "testClass" is added to the hidden input element.

A Dojo sample for reproduction: https://dojo.telerik.com/IsTnGqsk

### Expected/desired behavior

Any custom attributes must be added to the parent element with class "k-timedurationpicker".

### Environment

* **Kendo UI version: 2025.2.520
* **jQuery version: 3.7.1
* **Browser: [all]

### Bug report

When setting autoWidth: true and expanding a node, the popup's width is not adjusted based on the displayed child nodes.

### Reproduction of the problem

1) Enable the autoWidth option and open the DropDownTree.

2) Expand an item. A horizontal scrollbar appears and the width of the popup is not adjusted as expected:

A Dojo sample for reproduction: https://dojo.telerik.com/faeuFFwb/2

### Expected/desired behavior

The width of the popup must be automatically adjusted when expanding an option and the "autoWidth" option is enabled.

### Environment

* **Kendo UI version: 2025.2.702
* **jQuery version: 3.7.1
* **Browser: [all]

### Bug report

When the virtualization is enabled, in some cases, the selected options in the dropdown do not match the selected options in the input. 

### Reproduction of the problem

1) Create a MultiSelect with Virtualization (for example, the same configuration as in the online demo).

2) Select multiple options from the dropdown.

3) Enter a search entry in the input to filter the displayed options and select a specified option.

4) Scroll down and select another option.

5) Remove some of the already selected options through the input.

6) Open again the dropdown. The selected options in the input do not match the selected options in the dropdown.

A screencast for reproduction: https://app.screencast.com/v6GtyST0dQAnh

### Expected/desired behavior

### Bug report

When subscribing to the "requestStart"/"requestEnd" events of the DataSource after the Grid's initialization, the events do not fire during the Excel export.

### Reproduction of the problem

1. Enable the server operations of the Grid's DataSource.

2. Get a reference to the Grid and handle the DataSource "requestStart"/"requestEnd" events by using the bind() method.

3. Export the Grid's data to Excel through the built-in command.

4. The "requestStart"/"requestEnd" events do not trigger when the read request is activated.

A Dojo sample for reproduction: https://dojo.telerik.com/eyiDIGeM

### Expected/desired behavior

The  "requestStart"/"requestEnd" events must trigger when exporting the Grid to Excel.

### Environment

* **Kendo UI version: 2024.3.806
* **jQuery version: 3.7.0
* **Browser: all

Bug report

Even if a message file is added, the command buttons and the popup title in the Grid are not localized

Reproduction of the problem

1. Open the Dojo examples:

• Dojo with messages file - https://dojo.telerik.com/CehWjRrE
• Dojo with overriding the kendo.ui.Grid.prototype.options.messages - https://dojo.telerik.com/RWCxqxIm

2. Decrease the size of the screen so the Grid to be displayed in adaptive mode.
3. Click on a row and select the 'Edit' button to open the Edit popup

Current behavior

The command buttons and the dialog title are not localized:

Expected/desired behavior

It should be possible to change and localize the messages texts.

Workaround

 function onEdit(e){
      e.container.closest('.k-window').find('.k-window-title').text('My custom text')
      e.container.closest('.k-window').find('.k-button[ref-update-button]').text('Button Update Changed');
      e.container.closest('.k-window').find('.k-button[ref-cancel-button]').text('Button Cancel Changed');
 }

Environment

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

------------------- AI Summary -------------------

There appears to be a bug in the Grid component when used with a ContextMenu. To reproduce:

1. Create a new Telerik ASP.NET Core MVC application using version 2026.2.520 and select the “Grid and Menu” template.
2. In Index.cshtml, add .ContextMenu() to the Grid, then build and run.
3. Right-click a row → the context menu appears (expected).
4. Stop debugging,
5. remove .Scrollable() from Index.cshtml, and run again.
6. Right-click a row → the context menu does not appear (unexpected).

--------------- End of AI Summary ---------------

Bug report

When a custom bundle is created the kendo.aspnetmvc script is not placed on the correct order. Thus, in some scenarios errors occur. For example if a custom kendo script is created using the following kendo-config.json and MultiColumnComboBox is used with ServerFiltering enabled and error will be thrown:

{
  "version": "2026.2.520",
  "components": [
    {
      "file": "kendo.aspnetmvc.js",
      "features": []
    },       
    {
      "file": "kendo.dropdownlist.js",
      "features": []
    },
    {
      "file": "kendo.multicolumncombobox.js",
      "features": []
    }
  ]
}

Reproduction of the problem

1. Run the attached sample. In the sample a custom bundle as explained above is used. TelerikAspNetCoreApp1.zip
2. Try to select values in the DropDownList or MultiColumnCombobox

Current behavior

The bundle builder allows kendo.aspnetmvc.js to run before the widgets whose UI for ASP.NET Core helpers it augments. The data in the components is not filtered and the following error is thrown:

Uncaught TypeError: kendo.ui.MultiColumnComboBox.requestData is not a function

Expected/desired behavior

The kendo.aspnetmvc.js schould be ordered correctly by the custom script builder, so errors to be avoided and the components to work as expected.

TicketID:

1716198

Environment

• Kendo/Telerik version: 2026.2.520
• Browser: [all ]