Hello,

In the documentation for the Kendo jQuery ToolBar, there is support listed for button group 'items.buttons.toggle' if the button is of type button and has 'togglable' set to true. However, it seems that if that button group is set to "overflow: 'always'" the toggle method stops functioning, even if the button is listed as togglable.

I've recreated the issue in this dojo:
https://dojo.telerik.com/OPebOsEC/5

Is the toggle method unsupported for overflow buttons? If so, I can't find any reference to that in the documentation.

Thanks!

Bug report

When a template item is configured and overflow is set to 'always', the item remains in the main part of the ToolBar (not in the overflow popup). The item is displayed in the oveflow popup only if its text is long e.g. it behaves as its overflow option is set to 'auto'

Reproduction of the problem

1. Open the Dojo
2. Resize the rigth pane

Current behavior

The template item is rendered either in the main part of the ToolBar or in the overflow popup, based on the ToolBar`s width

Expected/desired behavior

An item with overflow set to 'always' should be displayed always in the overflow popup.

The issue is a regression starting with 2023 R1 (2023.1.117)

Workaround

The template element is rendered, but with the 'k-hidden' class. Remove the template from the configuration and set only the overflowTemplate. Subscribe to the overflowOpen event and remove the k-hidden class from the needed element:

overflowOpen: function(e){
      setTimeout(function(){
        $('.k-animation-container-shown .k-hidden').removeClass('k-hidden');
      },500)
    },
    items: [
      ....                      
      {
        //template: "<div><label> Labels some text content text text text: </label><input id='labels' style='width: 150px;' /></div>",
        overflowTemplate: "<div><label> Labels: </label><input id='labels' style='width: 150px;' /></div>",
        overflow: "always"
      }
    ]

Dojo - https://dojo.telerik.com/@NeliKondova/UMAvoDEg

Note: The explanation in the following api section should be revised, as the overflow could be set not only to buttons but to the other items as well:

• https://docs.telerik.com/kendo-ui/api/javascript/ui/toolbar/configuration/items.overflow

Environment

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

Bug report

When adding a new item in the ToolBar it is aligned on the right and before the overflow button.

Reproduction of the problem

1. Open the API demo - https://demos.telerik.com/kendo-ui/toolbar/api
2. Add multiple items (Button, SplitButton, etc.)

Current behavior

New items are added on the right side and are placed after the overflow button.

Expected/desired behavior

New items should be rendered next to the already existing items and before the overflow button.

The issue is a regression starting with 2023 R1 SP1 (2023.1.314) release

Environment

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

The Kendo UI Toolbar widget supports navigating between toolbar items using the TAB key if the navigateOnTab option is set to true. However, if the page is resized after the widget's creation so that more items are visible (i.e. not overflown) than before, those items are not reachable via keyboard.

This DOJO demonstrates this behavior: When the toolbar is created, the container is only 300px wide, which offers room for the first three items only. When setting the width back to "auto" afterwars, the rest of the items moves back out of the overflow menu, but cannot be focused.

Calling resize() does not help.

The Kendo UI Toolbar supports navigating between toolbar items uing the TAB key if the navigateOnTab option is set to true. However the overflow button which opens the overflow menu is not reachable by keyboard.

This DOJO demonstrates the behavior.

The Kendo UI Toolbar widget supports enabling/disabling items via the various enable options for items, splitButtons and buttonGroups or after initialization via the enable() method. In this DOJO, I have created a toolbar with a splitButton that contains several sub-items. As you can see, I have disabled the second sub-item via the options.

However, after disabling and enabling the whole splitButton, the second sub-item is no longer disabled and can be used normally although its enabled property has never been touched.

Since the "main" item of a splitButton is an item on its own that a dedicated click-action can be assigned to etc., I would not expect the enabled property to effect its sub-items.

The Kendo UI Toolbar widget supports adding attributes to the created DOM elements of items via the various attributes options for items, splitButtons and buttonGroups. I wanted to use this feature for adding custom CSS classes to sub-items of splitButtons. However, this seems to stop the "k-item" and "k-menu-item" classes from being added to the "li" DOM element. The sub-item is no longer clickable. This DOJO demonstrates the behavior.

The problem can be fixed by re-adding those classes manually in addition to the custom CSS class.

I have not tested what happens when custom CSS classes are added to usual items or items in buttonGroups.

When using the Kendo UI Toolbar widget together with the Tooltip widget, the following problem occurs:

In this DOJO, I have created a toolbar that contains a splitButton with several sub-items. The first sub-item has a title attribute that was set using the attributes option. The tooltip was configured to be active for all items with title attributes. As you can see, the active-styling is applied to the first sub-item as soon as the user hovers over it, although the item is not active an has not been clicked or executed in any other way. This does not happen for the other sub-items - they do not have any tooltips.

The wrongly added styles originate from the .k-active class that is added as soon as the tooltip becomes visible.