I am trying to upgrade to jQuery 3.5.1 and as per the documentation regarding compatible KendoUI versions I have upgraded KendoUI to v2021.1.119 (R1 2021). Now even though this version is compatible, I am getting warning messages from jQuery Migrate plugin as follows:

Wondering if this issue is known and support for the issue is on its way. Or else is it reccomended to change the minified JS files as these seems to be simple fixes.

Thanks!

Hello All,

There should be a feature where we can place radio button group in a matrix format (multiple rows with one header row). It would be very helpful in designing surveys.

Thanks

When a task contains a child task in this scenario we are we are looking for resizing the parent task individually as well as we should be able to resize the parent task along with its corresponding child tasks.

In my project, I'm trying to implement the above scenario but I could not finding anything relevant in the blog.

If the element has the child item so is there a way to resize the parent task also?

Is this feature already implemented?

Hi,

When I call grid.datasource.sync() on a datasource that has a model id defined, but this field is unmapped, I get a cryptic error. You can find a reproducer here: https://dojo.telerik.com/iLacazot

Uncaught TypeError: o is undefined
    setup http://127.0.0.1/a/kendo-ui/js/kendo.all.min.js:28
    create http://127.0.0.1/a/kendo-ui/js/kendo.all.min.js:28
    _promise http://127.0.0.1/a/kendo-ui/js/kendo.all.min.js:28
    Deferred jQuery
    _promise http://127.0.0.1/a/kendo-ui/js/kendo.all.min.js:28
    _send http://127.0.0.1/a/kendo-ui/js/kendo.all.min.js:28
    sync http://127.0.0.1/a/kendo-ui/js/kendo.all.min.js:28
    <anonymous> http://127.0.0.1/a/program/discount/search/:4058

On a slightly related subject; When checking the docs on the model id it seems that the example is missing from this page:

https://docs.telerik.com/kendo-ui/api/javascript/data/model/fields/id

Hi,

The `alwaysVisible` option is ignored when we have an external DataSource.

Consider the following code:

```

var dataSource = new kendo.data.DataSource({
   pageSize: 2,
   data: [
       { name: "Jane Doe", age: 30 },
       { name: "John Doe", age: 33 }
   ]
});

$("#grid").kendoGrid({
   columns: [
       { field: "name" },
       { field: "age" }
   ],
});
var grid = $("#grid").data("kendoGrid");

grid.setDataSource(dataSource);

grid.setOptions({
   pageable: {
       alwaysVisible: false
   }
});

```

Here, since the `pageSize=2` and we have `2` records; I don't expect to see not the pagination and other pager options after `alwaysVisible` is set to `false`.
However, I do see them since `alwaysVisible` is completely ignored.

When I move the datasource back inside the `$("#grid").kendoGrid({})` everything works as expected.

Please let me know if this is an bug or I have mistaken in understanding something about the options.

Thanks,

Ajay

When the Grid is rendered inside of a ListBox, the edit of a cell is immediately cancelled due to the focus being stolen from the ListBox.

https://dojo.telerik.com/iYuDAwIp/3

Hi

  It would probably be trivial to make the columnReorder much more useful

(1) Allow a preventDefault feature, to conditionally prevent some columns being moved. For extra points you could do this via a new columnReorderStart event so that the user can't drag the columns at all

(2) Don't allow locked columns to be moved out of the locked section

Thanks

The behavior of DropDownList, ColorPickers and probably more controls changes when a tooltip is added to them. When the tooltip opens, the ".k-state-border-down" CSS-class is added to the (e.g. DropDown) container. However, in the context of the DropDown, this class means that the DropDown is opened and therefore, the styling changes accordingly.

The following two DOJOs demonstrate this bug:

• Here, a DropDown without a tooltip works correctly: https://dojo.telerik.com/AvAxuQaK
• Here, a DropDown with a tooltip displays an unwanted shadow below the control: https://dojo.telerik.com/OGAVEzUb

We currently experience this behavior in the Editor widget when adding tooltips to tools that render the aforementioned controls.

Bottom navigation is obviously at the bottom in portrait mode, but on small screens in landscape mode it is detrimental to scrolled content.

It makes sense to keep bottom navigation on the small side of the screen but this requires to lock the app in portrait mode.

While allowing a change of orientation, it would be nice to have the option to show the bottom navigation on the right side and rotate the items when changing orientation to landscape and then back to the bottom when changing orientation to portrait.

The Popup widget has a"collision" setting that is documented here: https://docs.telerik.com/kendo-ui/api/javascript/ui/popup/configuration/collision. The documentation states the following:

If two words are used, the first one applies to the horizontal dimension and the second one - to the vertical dimension.

However, the first word sets the vertical behavior and the second word sets the horizontal behavior. This can be seen in the following DOJO: https://dojo.telerik.com/ewOKOZIh. The popup uses a configuration with its collision set to "flip fit". Still, when resizing the window horizontally (making it less wide), the popup slides under the input control instead of flipping to the other side. When resizing the window vertically (making it less high), the popup flips to the upper side of the input control once the space below is becoming too small.

In my understanding, the exact opposite behavior is expected.

When exist directory in directory, there's position bug in Tree View.

1. Open parent directory in Tree View.

2. Click the child directory more than once. (Click 5 times in a row)

3. Show parent directory's position. (Create an infinite number of 'k-treeview-toggle' classes in the parent directory each time the child directory is clicked.)

Demo: Kendo UI Snippet | Kendo UI Dojo (telerik.com)

Hello, 

We have a project using kendo-angular with kendo-ui for jquery for some components (spreadsheet, gantt, datepicker, context-menu,..)

When we started the project we followed this doc https://www.telerik.com/kendo-angular-ui/components/framework/kendo-jquery/

I updated all our @progress/kendo-angular-xxx dependencies to latest versions and also kendo-ui to latest 2022.1.119

When I run the project with ng serve and the site starts, we directly have an error coming from kendo.colorpicker

Cannot read properties of undefined (reading 'options')     at kendo.colorpicker.js:279:181

I created an empty project with our dependencies and was able to reproduce the error. Please see attached zip file.

npm install  ->  npm run start   ->   http://localhost:4200/

Here the kendo dependencies we have:

"@progress/kendo-angular-buttons": "^7.0.2",
"@progress/kendo-angular-charts": "^6.0.0",
"@progress/kendo-angular-common": "^2.0.2",
"@progress/kendo-angular-dateinputs": "^6.0.0",
"@progress/kendo-angular-dialog": "^6.0.1",
"@progress/kendo-angular-dropdowns": "^6.0.1",
"@progress/kendo-angular-editor": "^3.0.4",
"@progress/kendo-angular-excel-export": "^4.0.3",
"@progress/kendo-angular-grid": "^6.0.3",
"@progress/kendo-angular-inputs": "^8.0.4",
"@progress/kendo-angular-intl": "^3.1.2",
"@progress/kendo-angular-l10n": "^3.0.3",
"@progress/kendo-angular-label": "^3.1.2",
"@progress/kendo-angular-layout": "^6.5.0",
"@progress/kendo-angular-pdf-export": "^3.0.3",
"@progress/kendo-angular-popup": "^4.0.4",
"@progress/kendo-angular-ripple": "^3.0.3",
"@progress/kendo-angular-toolbar": "^5.0.0",
"@progress/kendo-angular-treeview": "^6.0.0",
"@progress/kendo-data-query": "^1.5.5",
"@progress/kendo-drawing": "^1.16.2",
"@progress/kendo-licensing": "^1.2.2",
"@progress/kendo-theme-material": "^5.1.1",
"@progress/kendo-ui": "2022.1.119",

Regards,

Thierry FRITZ

Requesting a modification to any component that uses k-animation-container.

Some components have this capability:

popup: {
    appendTo: $("SOME ID")
}

This gives us the ability to modify CSS for a single/particular popup. Please add this ability to all relevant components.

Or any other method to modify the styling of a particular dropdown. In some cases, there's an ID that's added but is removed for some reason when adding a certain configuration.

Bug report

The download functionality of the PDFViewer component and when downloading PDF using kendo.saveAs() method doesn't work on some iOS mobile devices.

Reproduction of the problem

1. Open the PDFViewer demo or the PDF Export Demo
2. Try to export the file to PDF on iOS device

Note: On some iOS devices the PDF is exported as expected, but on others, nothing happened.

Current behavior

Currently, on some iOS devices, the PDF is exported, on others, it is exported, but there is a warning "This form is not secure, are you sure you want to submit it". After approval, the file is downloaded. On some iOS devices after clicking the button to download the PDF file nothing happens.

Expected/desired behavior

It should be possible to download the PDF file on all iOS devices.

Environment

• Kendo UI version: 2022.1.301
• Browser: [iOS XX Safari]

As of today, the Datasource seems to be fully compatible with OData-v4, however, when server-side grouping and aggregation is enabled, we still need to provide a parametermap to correctly encode the group[] and group[aggregates[]] into the URL.

The OData specification should be followed and the URL build by the Datasource when the type is set to "odata-v4":

$apply=groupby((Field1, Field2))

or

$apply=grouppy((Field),aggregate($count as CountField))

thus saving the developers from providing their own encoding implementation.

Kendo introduced a setting for each filter to be case sensitive or not, depending on a setting or derived by defaults (like case-insensitive for 'contains').

https://docs.telerik.com/kendo-ui/api/javascript/ui/grid/configuration/columns.filterable.ignorecase

However, when the Datasource for OData-v4 builds the filter, the setting is ignored and the filter always looks like:

$filter=Field eq 'Test'

or

$filter=contains(Field, 'Test')

A custom parameter map is needed to fix that behavior, however, it should be provided by the datasource directly. A case insensitive filter should look like this:

$filter=tolower(Field) eq 'test')

or

$filter=contains(tolower(Field)), 'test')

where 'test' has been transformed of the entered search value with: value.toLowerCase().

The ContextMenu widget supports navigating from one item to another using the up/down arrow keys. If an item is focused, it receives the "k-state-focused" class and highlights the item visually. However, as soon as this or any other item is hovered, all focus classes are removed and therefore the highlight disappears. When pressing the arrow keys again, it reappears again, but the focus always starts moving from the hovered item instead of the most recently focused item.

This behavior can be reproduced in the following DOJO: https://dojo.telerik.com/ACIpeYIm

• Open the contextMenu
• Press the "arrow down" key until e.g. "Item 4" is focused
• Hover e.g. "Item 2" with your mouse, but do not click anything (now the focus disappears)
• Press the "arrow down" key again (now "Item 3" is focused, although "Item 5" would be expected to be focused)

Unfortunately, we currently don't really see any way to fix this without directly modifying Kendo code or rebuilding the entire keyboard navigation ourselves, because the contextMenu keyboard navigation does not seem to set the DOM focus at all, but works with CSS-classes only.

Do you have any suggestions?

Bug report

ContextMenu allows having focused and hovered items simultaneously.

Reproduction of the problem

Current behavior

There is an item marked with 'k-hover' class and an item marked with 'k-focus' class.

Expected/desired behavior

It is supposed to have a single active item in the ContextMenu.

Environment

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