split menu button - disabled only the primary button

[JohnHavok]

Discussed in #9384

^{Originally posted by JohnHavok February 14, 2023}
Hello everyone, I find myself in a situation where when using a Split Menu Button, I need to disable the primary button but not the menu associated with it.
The use of a disabled on the split menu button disables all, the button and the menu.
Do you know if it is possible to disable only the primary button ?

Is this a bug, enhancement, or feature request?

Feature Request

Briefly describe your proposal.

When using a Split Menu Button, it should be possible to disable the primary button but not the menu associated with it.

Which versions of Angular and Fundamental Library for Angular are affected? (If this is a feature request, use current version.)

latest

[JohnHavok]

The ticket is marked as completed but I can't see any MR associated with it. Is this a behaviour that wasn't intended and won't be added to the split-button or have I missed something?

[droshev]

@JohnHavok technically, the 'default' action is one of the actions available from the menu. It appears if selected from the menu. If this option is disabled, it is not possible to select it as 'default' from the menu. The design currently does not include separate disabled states. If you can provide a more detailed use case, we can present it to the designers for them to reconsider this feature.

[JohnHavok]

Example
In this example, using a split-button means that the user doesn't have to display the contents of the table without pagination and then check the select-all of fdp-table before clicking on the order confirmation button.
The "default" of split button should be disabled if no line is selected and it should still have access to the command all option.
And you could always make a more precise selection in several pages of the table and then click on the ‘default’ of split-button.
Save time, fewer clicks and fewer requests to a back end.