Hi team, 

I think there is a bug in the dependency detection.

In the attached "config_buged.js" i have chosen some components. The component "chiplist" was partially checked due to dependency.

When lunching my application I got the error :

Message: e(...).kendoChipList is not a function
    at init._createList (kendo.custom.min.js:91:8505)
    at new init (kendo.custom.min.js:91:3218)
    at init._attachGroupable (kendo.custom.min.js:133:96797)
    at init._groupable (kendo.custom.min.js:133:96348)
    at init._continueInit (kendo.custom.min.js:133:33864)
    at new init (kendo.custom.min.js:133:33735)
    at HTMLDivElement.<anonymous> (kendo.custom.min.js:1:42737)
    at jQuery.each (jquery-3.1.1.js:368:19)
    at jQuery.fn.init.each (jquery-3.1.1.js:157:17)
    at e.fn.<computed> [as kendoGrid] (kendo.custom.min.js:1:42713)

I was forced to totaly check the "chipList" component as seen in the attached file config.json

The Kendo-UI Diagram widget supports moving the whole diagram using the pan() method. However, the given offset does always have to be absolute.

Consider the following example:

The diagram is zoomed in and therefore not fully visible - assume a current offset of (-100, -100). The users should be able to pan using keyboard shortcuts. Whenever pressing one of the arrow keys, the diagram is moved in the corresponding direction by e.g. 50px:

If the user presses [ArrowRight], pan() needs to be called with an offset of (-50, -100).
If the user presses [ArrowUp], pan() needs to be called with an offset of (-100, -150).

However, since I do not know how much the diagram has already been moved, I cannot set the absolute offset required.

I have seen that pan() returns the current offset when being called without arguments, but this is not documented. Is this safe to use for that purpose or is there a better alternative? If yes, the documentation should be updated.

Line Chart Crosshair doesn't display on Tablets.

Display's fine on Desktop & also on Mobile, but tested on iPad and Android tablets the Crosshair line does not display.

kendo.2020.1.114

https://dojo.telerik.com/yBSdUQYS demonstrates the issue:

When a grid detail row is expanded, and pushUpdate() is called on it, the row collapses.

What is expected is for the grid row to remain in its prior state (expanded or collapsed.)

Until this is fixed, is there a work-around, other than manually re-expanding the detail row(s)? This is not a feasible work-around in which multiple nested grid rows are collapses and re-expanded, as this causes the UI to jump unexpectedly for the user.

i've tried to apply autoFitColumn method for treelist accordingly to the documentation, https://docs.telerik.com/kendo-ui/api/javascript/ui/treelist/methods/autofitcolumn#autofitcolumn , and seems it assumes only "simple" columns structure, i.e. no nested headers.

I am trying to upgrade my Kendo UI JQuery installation from 2022 to 2024 and it is not going smoothly. One issue I'm having is that now my grids with locked columns do not span the whole width of their container. In the old version, the k-grid-table would expand to fill the width of the k-grid-content but now it seems that the columns retain their width, rather than growing like they used to. So now there is a large white space between the last column and the vertical scrollbar. I did notice that if I remove the inline style in the developer tools that is applied to the k-grid-table in the unlocked section, it fixes it. It should continue to expand all columns evenly to fill the available width like it did in versions past or this should be an option that the user can set. To leave that space without any user choice is a bug.

Old Version:

New Version: 

Note, I reported this in a forum post. I know I can write code as a workaround but that is cumbersome, especially when I have many grids and multiple developers working on the project. 

In the latest version of Kendo UI, various input controls like the NumericTextBox or the ColorPicker now consist of an input field and a button control (used for increasing/decreasing the value or opening the dropdown).

The border-radius for those widgets can be controlled by setting the "rounded" option. At the same time, when using SASS themes, a button's default border-radius might be set using the $kendo-button-border-radius variable. The buttons inside e.g. a NumericTextBox do not override the theme's border-radius which leads to an outcome like this:

Widgets that use Buttons internally (and therefore offer no way of overriding the button's border-radius by setting its "rounded" option manually) should override the default styles.

Unfortunately, I could not reproduce the behavior in a DOJO, because I cannot transpile SASS themes there.

Context: There is an item that illustrates the issue here: https://www.telerik.com/forums/kendo-datepicker-value-not-populated-after-refresh-firefox-only

In Firefox, when using the asp-for tag helper to bind a c# DateTime field to an input element, then calling kendoDatePicker() on that element, the control fails to populate on a soft-refresh (F5). Upon reloading using F5 in Firefox, the input's type is set to datetime-local, and the input 's control variation is changed to the default date picker.  Then, the Kendo UI DatePicker is initialized with a blank input which normally has a type of text. 

Example project and video of issue are attached.

This is the pertinent code (also happens in latest version of Kendo as well):

    public class IndexViewModel
    {
        public DateTime DateAsDateTime { get; set; }
    }

        public IActionResult Index()
        {
            return View(new IndexViewModel { DateAsDateTime = DateTime.Today });
        }

@model IndexViewModel

<input id="dtDate" asp-for="@Model.DateAsDateTime">

<script type="text/javascript">
    $(document).ready(function () {
        $("#dtDate").kendoDatePicker();
    });
</script>

Bug report

The DropDownTree allows us to configure its checkChildren and filter options. Both options are working correctly, when used separately.

When the two options are defined for the DropDownTree, the checkChildren options don't select the child elements of a given node that is checked.

Reproduction of the problem

1. Open this Dojo example
2. Expand the DropDownTree popup
3. Check the "Furniture" node checkbox

Current behavior

Only the "Furniture" checkbox is being checked

Expected/desired behavior

The "Furniture" and all of its child nodes should be selected when clicking on the "Furniture" checkbox.
Here is a Dojo example in which the checkChildren configuration is working as expected.

Environment

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

Hi,

When I double click a cell and enter into editing mode, scrolling up or down will make the editor div out-of-place. 

It should follow the target cell instead.

This can be easily reproduced here: https://demos.telerik.com/kendo-ui/spreadsheet/index

It seems Kendo UI for Angular/React also have the same issue.

Reproduction of the problem

1. Follow the steps described in the link here - https://github.com/telerik/kendo-ui-core?tab=readme-ov-file#building-kendo-ui-core
2. Create a custom script for validator npx gulp custom -c validator
3. Try to load the script and create the components

Current behavior

The validator is not working, error is shown

jQuery.Deferred exception: $(...).kendoNumericTextBox is not a function

Expected/desired behavior

The components should work as expected when custom script is created

Hello Team,

We are currently facing challenges with the Kendo grid, which is a widely used widget or component at o9Solutions. Although we have been using Kendo for a long time, the widget is failing to meet accessibility standards for some components, which are crucial in today's world.

Regarding the Kendo grid, there is an issue where SR is reading the table twice, once for the header and once for the cells. This can cause confusion for assistive technologies like SR.

Consider the cases of horizontal scroll or fixed column cases also.

Having a single <table> is the standard. We can't create multiple tables, which will violate the good coding practices + accessibility standards.

---

I saw some posts regarding this... where it was mentioned we can remove this Scrollable() . But what are the cons of this if we remove this?
--

We want this functionality like a horizontal or vertical scroll or fixed column cases.But it needs to recognize as a single table.

1. Are there any specific versions of Kendo UI jQuery that you would recommend for compatibility with strict CSP?
   
2. What potential risks or extensive modifications might be involved in upgrading from our current version to a CSP-compatible version?

Repro steps:

• Open URL: Kendo UI Snippet | Kendo UI Dojo (telerik.com)
• Navigate to the Choose Library combo box and select 'Kendo UI 2022 R2' option.
• Navigate to the Run button and activate it.
• Open Narrator using 'Ctrl + Win + Enter' key.
• Press 'T' key to navigate table in quick navigation mode.
• Navigate the table header controls using up arrow.
• Observe that narrator announce role as link on Filter controls.

Actual Results:

Incorrect role is defined as "link" for the "filter" button, Screen reader announce like "Metric type filter column setting link".

Expected Results:

Correct role should be defined as "button" for the "filter" button. Screen reader should announce like "Metric type filter column setting button".

Hi Guys,

I have just upgraded to v2023.3.1114 only to find out the AngularJS directives have been completely removed from this release, causing a lot of wasted time & effort triaging the errors and then rolling things back to a previous working revision.

Back in a February 2018 blog post, you stated you were dropping support for AngularJS in all new components which was understandable but what I didn't expect was it's complete removal, especially in a SP, without any further communication.

The v2023.3.1114 release notes do not even list this as a breaking change, so are you expecting your customers to be clairvoyant now or is this just another example of how poor Telerik's customer service has become in the past few years?

Regards
Alan

I have a tab control, and a number of the related views contain grids.

If a grid is created in a tab view that is not visible, then the grid pager renders as if it was on a tiny mobile screen. The only way you can make it render the pager correcly is to manually resize the browser window after the grid has become visible.

I have a simple demonstration here: https://dojo.telerik.com/eCuQAqEm

The behavior is the same in both Chrome and Firefox.

<!DOCTYPE html>
<html>
<head>
    <base href="https://demos.telerik.com/kendo-ui/tabstrip/index">
    <style>html { font-size: 14px; font-family: Arial, Helvetica, sans-serif; }</style>
    <title></title>
    <link href="https://kendo.cdn.telerik.com/themes/6.7.0/default/default-main.css" rel="stylesheet" />
    <script src="https://kendo.cdn.telerik.com/2023.2.829/js/jquery.min.js"></script>
    
    
    <script src="https://kendo.cdn.telerik.com/2023.2.829/js/kendo.all.min.js"></script>
</head>
<body>
        <div id="example">
                <div class="demo-section">
                        <div id="tabstrip">
                            <ul>
                                <li class="k-active">
                                    Visible Grid
                                </li>
                                <li>
                                   Hidden Grid
                                </li>
                            </ul>
                           
                            <div>
                              <div id="visibleGrid"></div>
                            </div>
                            <div>
                              <div id="hiddenGrid"></div>
                            </div>
                        </div>
                </div>
            <script>
              	const data = [];
              	for (let i = 0; i < 100; ++i) {
                  data.push({
                    columnOne : `Item ${i} Column One`,
                    columnTwo : `Item ${i} Column Two`
                  });
                }
              	const gridOptions = {
                	dataSource: data,
                  pageable: {
                    refresh: true,
                    pageSize: 10,
                    pageSizes: [10, 20, 30]
                  },
                };
                $(document).ready(function() {
                    $("#tabstrip").kendoTabStrip();
                    $("#visibleGrid").kendoGrid(gridOptions);
                  	$("#hiddenGrid").kendoGrid(gridOptions);
                });
              
            </script>
        </div>
</body>
</html>

Hi Team, we're using kendo heavily on our platform. But still there're many gaps in kendo accessibility. I'm working as a Accessibility advocate and i believe every individual can access the widgets irrespective of their barriers. One of the issue is:

Keyboard Support is missing in the input fields buttons like:

1. Clear Button

2. Dropdown "arrow" Button

3. Date and Time Button

Current Behavior:

Focus is going to input field and you can write inside the combobox or textbox or multiselect but you can't interact with other icon buttons like dropdown , date & time, clear "x" button using tab key.

Expected Behavior: As per accessibility , every interactive elements needs to be keyboard focusable using tab key irrespective of shortcut.

I've created a feature request long ago and suggested solution for this: please check in the feature, it's declined by the team:

Date time picker Keyboard Support is missing for date and time button because of (tabindex=-1)

Bug report

Missing Anti-CRSF tokens trigger security alerts when testing for security compliance with OWASP ZAP.

Reproduction of the problem

https://www.telerik.com/forums/how-to-resolve-absence-of-anti-csrf-token-alert-in-kendo-all-min-js-1559042

Current behavior

Expected/desired behavior

Environment

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