REPL example:

https://blazorrepl.telerik.com/wIEiduuB379xcqGZ08

Steps to reproduce:

1. First click on the primary button. The dropdown does not open which is expected.
2. After that click on the arrow button. The dropdown does not open, but it should.

Last working version is 6.0.2:

 https://blazorrepl.telerik.com/coOiRYkB42URZx2823

Setting the Id parameter assigns the same Id to both the primary and dropdown button HTML elements, which leads to redundancy.

I am experiencing an issue with UI for Blazor's SplitButton. When I click on the dropdown arrow initially, it correctly expands the dropdown list area. However, while the dropdown list area is expanded, if I click the arrow again, it does not close it, leaving the dropdown list area expanded. The exact behavior appears to be that the dropdown collapses while the mouse is pressed down over the arrow button, but when the mouse is released, the dropdown list area expands again.

Reproduction: https://blazorrepl.telerik.com/QnlPPdvv50aUXSKO14.

The desired behavior is that the split button arrow would toggle the dropdown list between expanded and collapsed states.

How to add a separator item in the SplitButtonItems collection?

The DropDownButton and SplitButton exhibit the following accessibility issues:

• The screen reader cannot read the items in the DropDownButton and SplitButton popup.
• When the DropDownButton is opened with Enter, the user cannot navigate the dropdown items with the arrow keys (tested in NVDA).

I recently upgraded the target framework to .NET 7 and the UI for Blazor package to 3.7. With this configuration in my WASM app, it looks like the OnClick event for the child buttons is sometimes not fired. It happens occasionally and not for all child buttons.

===

ADMIN EDIT

===

Last working version: UI for Blazor 3.6.1. and .NET 6. You may revert to that configuration until the fix is live.

 

I'd like to be able to programmatically open/close the popup of the SplitButton. For example, open it on click of the main button.

This will make it easier to have a dynamic list of options whose order can be preserved.

Otherwise, you need to use conditional markup (which puts newly made visible items at the end), or a @foreach over a descriptor model.