The Grid should allow switching between case sensitive and case insensitive filtering.

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

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;
}

Hi !

So I work with Kendo UI for JQuery and Kendo UI for ASP.NET MVC and recently I had to use your combobox and found that the search was not accent insensitive and that there were no options to make it so. I think it would be a wonderful feature to have. My dataSource contains a lot of names that could potentially have accents and it would be really great to includes thoses names when I filter without accent.

Thank you !

Currently, when you load a different Kendo theme on the page, the colors in the Charts and Gauges do not change and the components remain styled based on the originally loaded theme. In order for them to be styled by the new theme, the page must be reloaded.

It would be best, if the page reload can be avoided. For example, a method similar to the existing redraw() method could be implemented and it should be capable of detecting the currently loaded theme and redrawing the components accordingly.

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.

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]

<meta http-equiv="Content-Security-Policy" content="default-src 'self'; img-src 'self'; script-src 'self'; style-src 'self' unsafe-inline; font-src 'self' data:;" />

When a user types 7/8/201x into a DatePicker, 7/8/201 is what ends up getting sent to the server.  I believe an important function of a date-type-specific control or widget is to prevent the entry of bad data.  The picker should not allow the entry of any string that is not a valid date or is outside of the Min-Max range (if specified).  In fact, properly formatted dates typed into the textbox seem to ignore the Min-Max range.

No user entering a date of birth is going to use the month selectors.  He or she will type the date into the textbox.  The datepicker, out of the box, should not allow the entry of invalid or out of range dates. The developer should not need to write a custom validator for behavior that virtually everyone would want.

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

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]

This is the same as an existing feature request, which was marked as completed but it doesn't achieve what was originally requested.

Orgchart like the one in Telerik ASP.NET Ajax

The UI for ASP.NET MVC OrgChart component is missing functionality found in the UI for ASP.NET AJAX product.

The demos only show a small organisation dataset. With a large dataset (including up to 5 levels), I found the current MVC solution becomes unusable. For example, the vertical/horizontal scroll bar becomes tiny and navigation becomes difficult.

The extra functionality available in the AJAX works around issues, such as, zooming in/out and solves other basic requirements, such as Export to PDF.

Please make the AJAX Functionality and Application Scenarios available in the MVC product.

There is a Kendo Validation in addition to ASP.net MVC one. 

There is a need for a method or script to disable the Kendo Validation and enforce the code to follow rules we define in the model.

Currently we have to write validation bypass script for each field, but I am looking for a way to disable Kendo Validations for the entire project or/and for specific page and it follows validation rules from the MVC model.

In most cases, validations from the MVC are sufficient and there is no need for redundance validations from the telerik.