Bug report

If you set a class through the items.attributes configuration in the SplitButton, the respective button is unclickable

Reproduction of the problem

1. Open this example - https://dojo.telerik.com/IvakivUc/5
2. Try to click the Item2 button

Current behavior

The button is unclickable

Expected/desired behavior

ТThe button should be clickable

Environment

• Kendo UI version: 2023.1.117
• 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 ]

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 ]

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!

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.

Good Day,

I believe it would be useful to update the `add` method to include the added items data Object, as you need to provide one to add it in the first place, to the options.items array in the widget itself. It would be consistent with the design of the widget in the first place and can allow dynamic code to iterate over newly added items without catering for specific bespoke IDs

Thankyou for your time,

Regards

Nathan

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.

Many Kendo UI Widgets support enabling/disabling animations via their options. In our case, we always disable them. As of R1 2023, the toolbar widget does not support customizing or turning off animations and always slides in/out the options of splitButtons or the overflow menu.

To maintain a consistent look&feel, disabling animations should by supported by the toolbar as well.

Do you have any suggestions how this could be fixed in the meantime?

Currently, the Kendo UI Toolbar supports adding icons to items by setting the "icon" property as documented here. However, only Kendo's own icons are supported.

In other widgets (like the Grid), adding custom icons (to a toolbar!) is already possible by specifiying an icon class.

However, if you wanted a third-party icon (or one of your own) directly to a standalone Toolbar, you would need to create a whole new template from scratch or replace the DOM element after rendering or use some hacky approach like demonstrated in this DOJO. While the first one means a lot of work, the latter ones are both not very stable.

Therefore, I propose to extend the icon support for Toolbars in general. I can think of two different solutions:

1. Let the developer specify an icon class (like in the Grid) that is then written into the DOM.
2. Let the developer specify some sort of "content template" that is displayed e.g. in a button or a splitButton. This way any content may be displayed in a toolbar item and this also allows for more complex and customized styling regarding the layout of e.g. icon and text.

Assume there is a Toolbar with a splitButton that has a subItem. Both the splitButton and the subItem have clickHandlers configured. As long as the splitButton is not in the toolbar's overflow, everything is working correctly. However, when overflown, clicking on the subItem executes the clickHandler of the splitButton instead of the clickHandler of the subItem.

This behavior can be reproduced in the following DOJO: https://dojo.telerik.com/enanUKan/3. Watch the console output when clicking the splitButton/its subItem.

Two more hints:

• The bug does not occur when using Kendo UI versions < 2021 R1 SP1 (2021.1.224).
• The bug does not occur when the splitButton has no clickHandler.

Unfortunately, both options are no viable solution for us. Any suggestions?

The Kendo UI Toolbar supports keyboard navigation between its items either via TAB/SHIFT+TAB or the RIGHT and LEFT arrow keys (documented here). However, there are some issues:

• While the arrow keys cycle endlessly, the user needs to be able the "escape" this cycle when using TAB, otherwise parts of the page would be inaccessible by keyboard. This "breakout" does not work when navigating backwards (SHIFT+TAB) in some scenarios as this DOJO demonstrates. Also, when focusing "After" and pressing SHIFT+TAB, the focus jumps to the splitButton instead of the overflow anchor which is inconsistent with the way TAB alone works.
• When the last visible (not-overflown) item is a separator after a splitButton, the overflow anchor is not focusable via TAB at all. This can be witnessed in this DOJO. However, when combining the items differently, everything seems to work fine.

The Typescript definitions for Kendo UI define the kendo.ui.ToolBarOpenEvent as follows:

interface ToolBarEvent {
        sender: ToolBar;
        preventDefault: Function;
        isDefaultPrevented(): boolean;
}

interface ToolBarOpenEvent extends ToolBarEvent {
        SplitButton?: JQuery | undefined;
}

The event is also documented that way in https://docs.telerik.com/kendo-ui/api/javascript/ui/toolbar/events/open. However, the corrersponding method in kendo-toolbar.js:446-453 does the following:

open: function (e) {
    var isDefaultPrevented = that.toolbar.trigger(OPEN, { target: element });
    if (isDefaultPrevented) {
        e.preventDefault();
        return;
    }
    that.adjustPopupWidth(e.sender);
},

Bug report
Toolbar splitButton togglable not working since version 2022.2.621Reproduction of the problem

Reproduction of the problem:

Dojo demo: https://dojo.telerik.com/EvOpoWaj

The toggle event does not fire for splitButton since the 2022.2.621 release

Expected/desired behavior
Toggle event shall fire

Environment
Kendo UI version: 2022.2.621 or newer
Browser: [all]

Hello,

In 2022.3.1109(but starting in 2022.1.119) using the Bootstrap v3 theme(not sure about any of the others), when you have a ToolBar inside a TabStrip, disabled buttons are invisible instead of greyed-out.

A demonstration can be found here: https://dojo.telerik.com/@Stephen/ESuKUqAD

It is due to the opacity being set incorrectly to 0 due to changes in the CSS rules, specifically there is a now a ".k-tabstrip .k-button.k-disabled" rule that has a higher specificity than the "old" rules.

Current/broken rules:

The rules in the last version it worked(2021.3.1207):

While I'm sure I can figure out a workaround, an official workaround/fix would probably be better.

Thanks.

Bug report

Adding an anchor tag styled as a Kendo button to the Toolbar via a template does not navigate to the set url.

Reproduction of the problem

1. Run this dojo.
2. The first item in the ToolBar - the anchor tag, styled as Kendo button - will not redirect to the specified url.

Expected/desired behavior

Clicking on the first item should navigate to the set url, similar to plain anchor tag or a button command.

Environment

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