Bug report

When ToolBar with buttons is initialized in kendo.mobile.Application an error Maximum call stack size exceeded is thrown in the browser console

Reproduction of the problem

1. Open the Dojo example.

Current behavior

Currently, Maximum call stack size exceeded is thrown in the browser console

Expected/desired behavior

There should be no errors in the browser console when initializing a Toolbar in the mobile Application. - Working Dojo

The issue is a regression starting with 2022.1.119, introduced with commit: telerik/kendo@b728b2b

Environment

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

Hi Telerik Team,

We are using latest version (2022.1.412) of the Kendo jQuery tool set. The latest version of Kendo jQuery is using one of the older version of jszip 2.6.1, which is being tagged a vulnerable by our scanning tool. Can you please upgrade the version of jszip in your latest Kendo jQuery (KendoUIProfessional and Telerik.UI.for.AspNet.Mvc5)  

Hello Telerik Team,

we at COPA-DATA have a supposed problem with the results of the Whitesource Scanner.

According to Whitesource the Kendo UI LIbrary is including a Sub Library called "DocSuitePA".

According to Whitesource this is the Library Owner:

This Library is released under "European License 1.2" terms, which means for us a commercial distribution is not possible.

Could you please verify if this is a false / positive of the White source scanner or if this is an real issue inside the KendoUI Library.

Best Regards

Reinhard Mayr

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 ]

Hi,

I would like to report a bug with Spreadsheet control. The problem is when trying to import from JSON data into a specific sheet and there are more than 200 rows for import.

If number of rows to import is up to 200, it works correctly, but if number of rows is 201 or more, import is not correct - data starts to import into new columns.

See this simple reproduction: https://dojo.telerik.com/IFuxijEZ/2

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?

The API docs for CheckboxGroup (https://docs.telerik.com/kendo-ui/api/javascript/ui/checkboxgroup/methods/value) states: "If passing an empty array, the value of the widget will be reset and the checked state will be removed from the selected checkboxes." But if you do this, it does NOT clear out any selections.

Code demo: https://dojo.telerik.com/IJOtaReh

Code snippit:

<ul id="checkboxgroup"></ul>
<script>
    $("#checkboxgroup").kendoCheckBoxGroup({ items: [ "one", "two", "three" ] });
    var checkGroup = $("#checkboxgroup").getKendoCheckBoxGroup();
    checkGroup.value(["two", "one"]);
    checkGroup.value([]);
</script>

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().

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.

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]

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]

Greetings

Currently, all dynamically added elements are being added to the document body, unless we specify an appendTo option.
When we look at the Angular library, we can specify a default container element there via an injection token.
It'd be great (and not that much work) to have that for jQuery (and thus MVC) as well, since adding/removing elements to/from the body causes high reflow times.
In some components, like when we use a filterrow inside a Grid, we can't specify an appendTo option for those dropdownlists, so having a global setting would help there as well.  

I currently have to manually edit the kendo.all.min.js file every release to manually insert a fix for this, since adding things to the body causes terrible lag for us.

Kind regards

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.

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

Create a setting that will enable/disable the drag to select when Multiple Selection is enabled.

Current behavior

The Selectable widget which has drag selection functionality is always turned on, but in some cases it conflicts with other logic like drag and drop.

Expected/desired behavior

Create a setting to enable/disable drag-selection.

Environment

• Kendo UI version: all

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)

The popup widget provides a setOptions() method that allows to update the options after initialization (as documented here: https://docs.telerik.com/kendo-ui/api/javascript/ui/popup/methods/setoptions). However, setOptions does not update the collision settings. This can be witnessed in the following DOJO: https://dojo.telerik.com/UbiKumIg.

When reducing the window size until the popup is forced to change its position, it still uses the "fit"-behavior, although setOptions() has been called with "fit".

A quick check in the sources revealed that the widget caches the collision settings internally in a form that is easier to work with than the configuration string. However it is never updated on setOptions().

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.