raised Ticket 1710851, we want permanent fix from your side in next release, we don't rely on workaround that you have provided.

here is ticket desc-

We are using Telerik ASP.NET MVC with jQuery and are strictly following ADA compliance. We are facing an issue with DropDownList controls.

We have a required DropDownList, which we currently mark as required by passing the required HTML attribute. However, the problem is that Telerik places the required attribute on the <input> element, while screen readers interact first with the <span role="combobox"> element. As a result, the screen reader does not announce that the field is required.

Screen readers (tested with NVDA and VoiceOver on Chrome) only read required when it is applied to the element with role="combobox". We understand that having aria-required and role="combobox" on different elements is likely causing this behavior.

All we need is for the required state to be announced by screen readers, so any solution that achieves this is acceptable. Currently, the Telerik method of placing the required attribute is not accessible to screen readers.

In many applications we use passwords. Would love to have a field that allows for the setting of a type to "password" without templates. 

.PasswordTextField() or something similar. 

**Added by Admin**
If I pass in the model, the fields should get affected by the `DataType(Datatype.Password)` data annotation attribute.

Bug report

The jQuery dependency is defined as follows in the package .nuspec file:

<dependency id="jQuery" version="(, 3.7.1]" />

This causes the following warning to appear when installing the package in a project:

Telerik.UI.for.AspNet.Mvc5 2024.3.1015 does not provide an inclusive lower bound for dependency jQuery (<= 3.7.1). jQuery 1.4.1 was resolved instead.

The affected packages are:
Telerik.UI.for.AspNet.Mvc5
Telerik.UI.for.AspNet.Mvc5.Trial

Reproduction of the problem

Install the Telerik.UI.for.AspNet.Mvc5 package in a project and check the warnings list.

Current behavior

Warning:
Telerik.UI.for.AspNet.Mvc5 2024.3.1015 does not provide an inclusive lower bound for dependency jQuery (<= 3.7.1). jQuery 1.4.1 was resolved instead.

Expected/desired behavior

Add a lower bound (https://learn.microsoft.com/en-us/nuget/reference/errors-and-warnings/nu1604) to resolve the warning about the jQuery dependency.

Environment

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

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.

My understanding after talking to support is that a grid with a popup editor has code behind the scenes that stops adverse scrolling behavior when the popup window closes.  However, under certain circumstances, this doesn't work if you have a grid nested in your popup editor that also has a popup editor.  As it was described to me, this "behavior is not directly related to the Grid, but the Kendo Window. Generally, it provides the preventScroll property, but I am afraid this scenario is more complex due to the window being internally embedded into the Grid".

The exact scenario I found was that if you shrink you browser window small enough that you need to use some scrolling, scroll down your grid a little, then do something to cause the popup editor to open.  Scroll down again to get to your nested grid, open that popup editor, then close it.  The browser then auto scrolls to the top.

I was given this code to fix the issue (and it DOES fix it):

<script>
    kendo.ui.Grid.fn._destroyEditableOrg = kendo.ui.Grid.fn._destroyEditable;
    kendo.ui.Grid.fn._destroyEditable = function () {
        var that = this;
        if (that._editContainer) {
            var kw = that._editContainer.data().kendoWindow;
            kw.setOptions({
                modal: false
            });
        }
        that._destroyEditableOrg();
    };
</script>

The problem is that these fields aren't documented... I would never have figured this out on my own.  So my feature request is that either this behavior is fixed or these properties exposed from the Grid settings.  

-Steven

PS: For Telerik, the original ticket was 1589389.

Hello,

Request/suggestion to enhance the scheduling functionality. For production environments, especially with long running processes the current setup is not sufficient.

See excel for an example of how this could work. Extension of current timeline to include a year. Would be best if multiple timelines could be defined creating more or less detail depending on choices.

The other axis to relate to the resource/asset where the work will take place.

Currently the scheduler works best for short-running activities. Displaying longer running activities is a challenge.

I have a Kendo Notification component on my page. When the page loads, it is possible a notification needs to show immediately. This fails because the Notification component is not ready yet. Even putting this message show inside a document.ready() call does not work. There’s no rendered event on this component to know when Kendo has it added to the DOM and it is accessible. So I ended up creating an array of messages to show. And running a setInterval block on page load until it is ready to go. Then clearing the interval and message array. It’s a work around but it is hacky and it would be better if I could subscribe to an event that tells me when the notification component can be used.

Just like posted here (and declined) : http://kendoui-feedback.telerik.com/forums/127393-kendo-ui-feedback/suggestions/3844570-serialization-support-of-datasourcerequest-and-app

I would like to see a portable separate assembly that : 
- can be referenced both on ASP.NET MVC side and WCF server side.
- A DataSourceRequest and DataSourceResult class that serialize well in both SOAP and REST WCF.

Referencing Kendo from the Application server side also requires references to System.Web.Mvc, Razor pages, ... and others that shouldn't be necessary.

Row's hover effect should be optional and it could be enabled/disabled in grid's configuration, the same as we add Selectable, Navigatable, Sortable, Editable, etc., functionalities to grid. This could apply to odd/even coloring too. Should no need to do hacks to achieve this.

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.

<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:;" />