Currently, there is no built-in option to disable a button based on specific conditions. Although it's possible to work around this limitation by using dynamic SCSS or embedding HTML tags through widgets, these approaches demand extra coding effort and can complicate the development process.
Introducing a native feature that allows developers to set conditions for when a button can be enabled or disabled - similar to the conditional logic available for input widgets in higher MX versions - would be extremely valuable. This functionality is especially crucial in scenarios where a button should only become active after certain criteria have been met, such as ensuring all required fields in a form are completed before allowing submission. Even when a button is not clickable, it still provides important visual context, guiding users on the next steps they need to take.