Bug report
Vertical Menu with multi-level sub-menus and specified height for the sub-menu does not render the items correctly.
Reproduction of the problem
Open the following Dojo: https://dojo.telerik.com/ypHIRacj
Hover on `Mens` item.
Expected/desired behavior
Overflowing items shall be hidden and the scroller should scroll through the list.
Environment
jQuery: 3.4.1
Kendo UI version: 2024.3.1015
Browser: [all]
Bug report
Scrolling submenu in Scrollable Menu not available in 2024.1.319
Regression with v.2024.1.319
Reproduction of the problem
Open this Dojo example - https://dojo.telerik.com/aweLUguB
Hover over "Mens"
Expected/desired behavior
Scrollbar shall be rendered so user can scroll over the list items
Environment
Kendo UI version: 2024.1.319
Browser: [all]
The popupCollision option of the Menu cannot be set in MVVM
The popupCollision cannot be set
You should be able to set the option in MVVM scenario
Bug report
Vertical ContextMenu missing wrapper element <div class="k-menu-scroll-wrapper vertical">
Reproduction of the problem
Dojo: https://dojo.telerik.com/ObifIvOS/2
Result:
Environment
Kendo UI version: [2022.2.510 or newer]
jQuery version: [all]
Browser: all
Steps to reproduce:
Expected: New child list item under the "Fifth Item" menu is bold and purple
Actual: New child list item is not formatted
If you inspect the DOM for the appended item, you will notice that the list item was not appended to a ul. A child ul was created but it is empty and has an undefined id.
It looks like this bug was introduced in 2023.2.606
When utilizing the content property for a Kendo UI Menu's DataSource, the MenuItem's content is not created as expected based on documentation.
Here is a Progress Kendo UI Dojo which replicates the appearance issue.
This is a Dojo with an older version that is working as expected.
Define the content in a nested Items property:
{
text: "<b>Item 2</b>",
encoded: false, // Allows use of HTML for item text
items: [{
content: "text", // content within an item
contentAttr: {
style: 'border: 1px solid red; padding: 2px;', // Add attributes to the content container
custom: 'value'
}
}],
},
Here is a Dojo of the workaround in action.
When items are added to the Menu component using the append() method, the select event of the items is not triggered.
Regression introduced with 2023.2.606
The alert about the item selection is not appearing, i.e. the select event is not triggered.
The select event should be triggered and the alert should appear as expected.
When scrollable and closeOnClick are enabled and the user click on an item, the Menu does not close.
The Menu does not close.
The Menu should close after the user click on an item.
When you try to append a child item in the Menu, the parent item is replaced instead.
Regression introduced with 2022 R1
The new item replaces Sub Item 1
The new item should be appended as a child to Sub Item 1
When new item with sub-items is appended or inserted (before/after) into kendoMenu or kendoContextMenu then "aria-expanded='false'" text surprisingly appears right to the new item. This defect can be reproduced just by running the demos published for kendoContextMenu or kendoMenu's methods such as append, insertAfter or insertBefore, or as shown bellow. The defect is reproduced on Windows and Linux, as well as on Firefox, Chrome and Edge.
The contextMenu is not acessible. Upon opening, it should capture the keyboard focus and allow navigation by arrow keys, but it does not. (It can be observed here.)
Keyboard use of the contextMenu is also not documented. Keyboard use of the menu is documented here, while the contextMenu is separately documented here.
Currently, when an item is expanded in the Menu, the screen readers do not read which item/subitem is expanded. The 'aria-expanded' attribute is not added to the Menu.
https://www.w3.org/TR/wai-aria-practices/examples/menubar/menubar-1/menubar-1.html
The 'aria-expanded' is not added to the Menu and the screen readers do not inform which item is expanded
The screen readers should be able to read which item is expanded in the Menu.
I'm having resize issues with the Menu control that I cannot sufficiently document at this time (my menu is inside a splitter, it's horizontal and it should be scrollable, but the arrows don't always appear).
I tried working around them by manually forcing a resize. Per documentation:
Each Kendo UI widget has a resize()
method which can be used to trigger a layout readjustment instead of using kendo.resize
. The resize
method of the widget accepts a single Boolean parameter, which defines whether the control should execute its layout adjustment algorithm even if the widget dimensions have not changed ("force"
mode).
However, the Menu widget does not override this method. It only binds to the Window resize event:
$(window).on(RESIZE, kendo.throttle(function(){
that._setOverflowWrapperWidth(initialWidth, initialCssWidth);
that._toggleScrollButtons(that.element, backwardBtn, forwardBtn, isHorizontal);
}, 100));
It's highly probable that the magic value 100 does not fit my use case. However, I cannot force a resize neither by:
Possibly related to https://github.com/telerik/kendo-ui-core/issues/4067 .
### Bug report
Sub Menu item is not opened, if hovered before close animation of another sub-menu-items's child item completes.
Reported in ticket ID 1473199, where a reproduction video is available.
### Reproduction of the problem
1. Run the following [Dojo snippet](https://dojo.telerik.com/@Dimitar-Goshev/EfEmoCon)
1. Hover Item 1, then hover Sub Item 4
1. Hover Sub Item 41 to expand its sub item
1. Quickly move the mouse from SubItem 41 to Sub Item 4 text and then to Sub Item 3 text
### Current behavior
Sub Item 3 is NOT expanded and its child items are NOT visible
### Expected/desired behavior
Sub Item 3 is expanded and its child items are visible
### Environment
* **Kendo UI version:** 2020.2.617
* **Browser:** all
Dojo example.
The sub-menu of "Sub Item 1" does not open.
If the behavior is not exhibited on the first test, click another of the root items and repeat, or reload the example and try again. The issue is more easily reproducible in IE, however it occurs in Chrome and Firefox as well. For more details and a video demonstrating the issue, refer to Ticket ID: 1472421
Sub menus open consistently.
$("#context-menu").kendoContextMenu({
target: "#grid",
filter: "tr.k-state-selected[role='row']",
select: function(e) {
var grid = $("#grid").data("kendoGrid");
var model = grid.dataItem(e.target);
alert( model.age + " " + model.name);
}
});
Reproducible with version 2017.2.504 (R2 2017) and newer.
Dojo example.
Separators are not displayed.
Separators are displayed.
Workaround:
.k-menu-scroll-wrapper .k-menu-group .k-separator {
border-bottom: 1px solid #c5c5c5;
width: 100%;
}
Defining a custom namespace with Kendo.ns stops the displaying of all submenus in the Menu component.
This is a regression represented in R2 2019
The Menu component should work properly even when a custom Kendo namespace is being defined. To see the expected behavior put a comment on the following line:
kendo.ns = "kendo-";
I prepared a dojo example. https://dojo.telerik.com/oKIkuCaP
As can be seen from example, the MVVM context menu seems to ignore data-copy-anchor-styles option.
Current solution for us is to extend the kendo.ui.ContextMenu and set the copyAnchorStyles option to false.
Nested Menu items are not being expanded the first time that they are hovered: