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.

Follow-up of https://feedback.telerik.com/kendo-jquery-ui/1516557-typescript-definition-of-jquery-data-method-does-not-include-undefined

The mentioned type is still missing for:

- kendoAvatar

- kendoCheckBox

- kendoListView

- kendoOrgChart

- kendoRadioButton

Bug report

In mobile apps when a Button is clicked it is not getting focused. This leads to the focus not being removed from the previously focused element.

Reproduction of the problem

1. Open the Dojo
2. Type something in the input and click the Button.

Current behavior

The returned value of the TextBox is null as the Button is not focused and the TextBox is not focused out.

Expected/desired behavior

The Button should be focused when it is clicked, thus the TextBox to be focused out.

Environment

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

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 ]

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>

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]

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

Steps to reproduce the behavior:

1. Run the jQuery Virtualization Demo
2. Open the popup of the Widget

Expected behavior
The header and rows shouldn't overlap

Screenshots

Affected package

• seems to affect all Themes

Affected suites

• Kendo UI for jQuery

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.

Hello,

I've noticed that any attempt at calling `dataSource.read()` on a datasource attached to a Kendo Menu results in keyboard accessibility breaking.

Steps to reproduce:

1. Use this code as a starter: https://dojo.telerik.com/IJOyUzEX/2

2. Notice that tabbing to the menu works the first time 

3. Activate the menu and close it.

4. Now try to tab into the menu again. It does no longer work.

Are there any better methods to have Kendo Menu dynamically generate the list everytime an open event is triggered?

kendo.all.min.js is reporting this in Chrome.

A page or script is accessing at least one of navigator.userAgent, navigator.appVersion, and navigator.platform. In a future version of Chrome, the amount of information available in the User Agent string will be reduced.

To fix this issue, replace the usage of navigator.userAgent, navigator.appVersion, and navigator.platform with feature detection, progressive enhancement, or migrate to navigator.userAgentData.

Note that for performance reasons, only the first access to one of the properties is shown.

https://blog.chromium.org/2021/05/update-on-user-agent-string-reduction.html

When will this be resolved?