1. Create a solution with several Telerik UI for MVC projects

2. Perform a rename of a value that is present in multiple projects

Expected result: Rename is performed successfully.

Actual result: Visual Studio crashes.

In a Selectable grid, when only one column is shown in the grid, and the model's Id field is specified, an error occurs on selection.

If you include more than one column (must be more than one visible) it works correctly.

If the model's Id is not specified, it works correctly even with only one column visible. 

@(Html.Kendo().Grid<TelerikMvcApp1.Models.OrderViewModel>()
    .Name("grid1")
    .Columns(columns => {
        columns.Bound(p => p.ShipName);
        columns.Bound(p => p.ShipCity).Hidden(true);
    })
    .Pageable()
    .Sortable()
    .Scrollable()
    .Filterable()
    .Selectable(s => s.Mode(GridSelectionMode.Single))
    .HtmlAttributes(new { style = "height:430px;" })
    .DataSource(dataSource => dataSource
        .Ajax()
        .PageSize(20)
        .Read(read => read.Action("Orders_Read", "Grid"))
        .Model(m => m.Id("OrderID"))
     )
)

Bug report

Reproduction of the problem

1. Reference kendo.all.min.js and kendo.all.min.js.map in a project
2. Add a basic Grid:

<div id="grid"></div>
<script>
    // The dataSource is initialized as a stand-alone widget that can be bound to the Grid.
    var dataSource = new kendo.data.DataSource({
        transport: {
            read: {
                // The remote endpoint from which the data is retrieved.
                url: "https://demos.telerik.com/kendo-ui/service/products",
                dataType: "jsonp"
            }
        },
        pageSize: 10
    });

    $("#grid").kendoGrid({
        // The dataSource configuration is set to an existing DataSource instance.
        dataSource: dataSource,
        pageable: true
    });
</script>

3. Open the browser's dev tools Source tab and place a breakpoint (e.g., on line 3715).

Current behavior

The breakpoint is added at the last line (326079) of the file.

Expected/desired behavior

The breakpoint is added at the desired line (e.g., 3715).

Environment

• Kendo UI version: 2023.3.1010
• jQuery version: x.y
• Browser: [ Chrome XX]

My web page displays grids on multiple pages, and each grid has a pager with a page size control.

In recent updates the styling broke in all but one page.
In the case where I was creating the grid using Kendo UI for JQuery, it worked fine.
In the instances when I create it using MVC, there are styling errors. (See in the image how the number "10" is truncated.)




After much drilling into the HTML, I found the difference in how the Razor library creates the HTML elements, as opposed to how the JQuery creates the HTML elements.

JQuery generates the following element structure. Note that the k-pager-sizes element comes after the k-pager-numbers-wrap element

<div class="k-pager k-grid-pager k-pager-md"> <!-- The pager bar -->
     <div class="k-pager-numbers-wrap">
             <!-- ... -->
     </div>
     <span class="k-pager-sizes k-label">
            <!-- The page-size picker goes here -->
     </span>
</div>

In contrast, the Kendo Razor libraries generates the following element structure, where the k-pager-sizes element falls inside the k-pager-numbers-wrap element:

<div class="k-pager k-grid-pager k-pager-md"> <!-- The pager bar -->

     <div class="k-pager-numbers-wrap">
             <!-- ... -->
            <span class="k-pager-sizes k-label">
                  <!-- The page-size picker goes here -->
             </span>
     </div>

</div>

This breaks the styling. (I am using the bootstrap kendo theme) There is styling rule that imposes a minimum width on all buttons under .k-pager-numbers-wrap. This makes the drop-down arrow too wide, which causes the page size number to truncate.

    @each $size, $size-props in $kendo-pager-sizes {
        $_padding-x: k-map-get($size-props, padding-x);
        $_padding-y: k-map-get($size-props, padding-y);
        $_item-group-spacing: k-map-get($size-props, item-group-spacing);
        $_item-min-width: k-map-get($size-props, item-min-width);
        $_pager-dropdown-width: k-map-get($size-props, pager-dropdown-width);

        .k-pager-#{$size} {
            padding-inline: $_padding-x;
            padding-block: $_padding-y;
            gap: $_item-group-spacing;

            .k-pager-numbers-wrap {
                .k-button {
                    min-width: $_item-min-width;
                }

 My current hack workaround is to add a more specific CSS rule.

@import "@progress/kendo-theme-bootstrap/dist/all.scss";

.k-pager-md .k-pager-numbers-wrap .k-dropdownlist .k-button {
	min-width:inherit;
}

Bug report

Reproduction of the problem

Inspect the Grid in the MVC demos.

Current behavior

The Grid renders the k-widget class.

Expected/desired behavior

The rendering must be consistent with jQuery and Core and the k-widget class should not be rendered. The issue is specifically in the MVC Grid. The Kendo UI for jQuery and the Core Grid no longer render this class.

Environment

• Kendo UI version: 2023.1.314
• jQuery version: x.y
• Browser: [all]

Bug report

Regression in R1 2023.

Reproduction of the problem

1. Set the following HtmlAttributes configuration in a Grid column:

columns.Bound(p => p.OrderDate).HtmlAttributes(new { title = "Order Date: #=kendo.toString(OrderDate, 'dd-MM-yyyy')# " });

Current behavior

kendo.toString is not executed and as a result the date is not formatted. The exact value of the title attribute, as shown above is rendered as title of the cell.

Expected/desired behavior

The logic is executed and the OrderDate value is rendered in the title with the specified format.

Environment

• Kendo UI version: 2023.1.117
• jQuery version: x.y
• Browser: [all]

Please note the following MVC code:

Bug 1: The Window should have the top set by the Top() method. It does not. 

Bug 2: The Window should have the top set by the HtmlAttributes() method. That does not work either. 

Bug 3: The scrollable method also does nothing to the window. So this entire line seems to be omitted.

Bug 4: The window is supposed to be centered by the Kendo native code. It isn’t. The recurring editor div element is not shown until after the window centers. So the window generates, centers on the screen, then the recurring DIV is shown which expands the window downwards, then the window is shown. This makes it go off the bottom of the screen. I didn’t need vertical center anyways so I fixed this by setting the top to 40px. Which is when I ran into the above issues. However if I was not doing this, the center() issue would still be there. I fixed this in JavaScript on the event’s edit event.

Reproduction of the problem

1. Set a class in the TileLayout's HtmlAttributes, e.g.,

.HtmlAttributes(new { @class = "test" })

2. Inspect the rendering of the component.

Current behavior

The custom class is not applied to the TileLayout.

Expected/desired behavior

The custom class is applied to the TileLayout along with the pre-defined Kendo classes.

Bug report

After using setOptions() the HTML structure of Grids column header is different.

Reproduction of the problem

In the following demo:
https://demos.telerik.com/aspnet-mvc/grid/persist-state

1. Inspect the HTML structure of a column header.
2. Click the Load State button.

Current behavior

When the button is clicked, setOptions() called for the Grid and the structure of the column headers is now different.

Expected/desired behavior

When setOpitons() is called with no options that may affect the headers the HTML structure of the column headers should be the same.

Environment

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

Bug report

A regression introduced in R1 2022.

Reproduction of the problem

Reproducible with the RadioButton and RadioButtonFor helpers.

@Html.Kendo().RadioButton().Name("HealthA1").Label("Yes").Value(true).HtmlAttributes(new { id = "HealthA1_True" })
@Html.Kendo().RadioButton().Name("HealthA1").Label("No").Value(false).HtmlAttributes(new { id = "HealthA1_False" })

Current behavior

The rendering is broken: no label element is rendered, the Kendo classes are not applied to the input.

Expected/desired behavior

The RadioButton renders properly.

Environment

• Kendo UI version: 2022.1.301
• jQuery version: x.y
• Browser: [all]

Bug report

Regression introduced in R1 2022.

Reproduction of the problem

Reproducible in the demo: https://demos.telerik.com/aspnet-mvc/grid/search-panel

Current behavior

There is a difference in the rendering of the search panel.

MVC:

<span class="k-textbox k-grid-search k-display-flex">
    <input autocomplete="off" class="k-input" placeholder="Search..." title="Search..." type="text">
    <span class="k-input-icon">
       <span class="k-icon k-i-search"></span>
    </span>
</span>

Kendo UI for jQuery and Core:

<span class="k-searchbox k-input k-input-md k-rounded-md k-input-solid k-grid-search">
    <span class="k-input-icon k-icon k-i-search"></span>
    <input autocomplete="off" placeholder="Search..." title="Search..." class="k-input-inner">
</span>

As a result, in MVC the search panel's magnifying glass is displayed outside the input.

Additionally, the search panel's appearance in Kendo UI for jQuery and Core is different than the one in the previous versions. In R3 2021, the input is positioned on the left hand side of the Grid's toolbar and the magnifying glass appears at the right end of the input. In R2 2022, the input is positioned on the right side of the toolbar and the magnifying glass is displayed at the beginning of the input.
R3 2021 dojo
R1 2022 dojo

Expected/desired behavior

Positioning of the input within the toolbar and the magnifying glass icon within the input, to be as in R3 2021.

Environment

• Kendo UI version: 2022.1.119
• jQuery version: x.y
• Browser: [all]

The columns widths do not match the header and are slightly off, and after enough columns it is half a column out.

Bug report

Not reproducible with Sass themes.

Reproduction of the problem

https://dojo.telerik.com/ejaVeZUD/7

Current behavior

Map custom markers are not positioned correctly when zooming out using 'Less' themes

Expected/desired behavior

Markers are positioned correctly when zooming out.

Environment

• Kendo UI version: 2021.3.1109
• jQuery version: x.y
• Browser: [all]

Editor => Imagebrowser path for subfolder is url-encoded

if a picture from a subfolder is selected, the generated image-url is encoded for the subpath

encoding may be usefull, but not for the path separator

Bug report

Reproduction of the problem

1. Visual Studio 2019 version 16.8.3 (or another version the extension works with)
2. Install the Scaffolder extension.
3. In a sample Terlerik ASP.NET MVC Application verify that the Kendo Scaffolder and its configuration panel work as expected.
4. Update Visual Studio to version 16.9.2.

Current behavior

The Kendo Scaffolder is no longer available in the Add New Scaffolded Item dialog.

Expected/desired behavior

The Kendo Scaffolder works as intended.

Environment

• Kendo UI version: 2021.1.224
• jQuery version: x.y
• Browser: [all]

Hi,

We are using globalization with UI for ASP.NET MVC to translate control to French (fr-CA). However, while most messages are correctly displayed in French, there are some that are still displayed in English. For example, if we use the Grid control with filter on a 'string' column, the dropdown for the operators shows both French ("Commence par") and English ("Is empty") operators:

Looking at the source code, we can see that in ressource files "Messages.fr-FR.resx" and "Messages.fr-CA.resx", there are some messages that are still in English (for example, Filter_StringIsEmpty).

Note that corresponding text seems to be correctly translated in jQuery messages file (for example, "kendo.messages.fr-CA.js"), so it might only be a matter of applying the same translation to .resx files.

Note also that the same problem seems to be present in the source code of the latest version (2020.1.114).

Thanks! 

Passing a dynamic object to a template column builder throws an exception:

c.Template(m => { })
.ClientTemplate("<input type='checkbox' value='#= Id #' />")
.Visible(ViewBag.Can.Edit);

Using an explicit cast doesn't throw the error: