[Feature] Support "disabled" state for individual select options in the admin config

[rybkinevg]

Description

Currently, the Select, Multiselect and EditableMultisect form elements only supports the disabled attribute at the select element level, which disables the entire dropdown. There is no way to disable individual <option> elements within the select dropdown.

The current option properties supported are: label, value, title, and style. The feature request is to add support for a disabled property that can be passed from the source model to disable specific options while keeping others selectable.

Expected behavior

Support for a disabled key in the option array that accepts a boolean value (true/false)

Benefits

• Better UX: Allows developers to show unavailable options in dropdowns while keeping them visible for context, rather than hiding them completely or disabling the entire select element
• Standard HTML5 Compliance: The disabled attribute on <option> elements is part of the HTML5 standard and is widely supported across browsers
• No Breaking Changes: The feature is additive and maintains full backward compatibility with existing code
• Cleaner Conditional Logic: With native disabled support, conditional option availability can be handled directly in the source model with simple boolean logic, reducing JavaScript dependencies and improving maintainability

Additional information

Example:

public function toOptionArray(): array
{
    return [
        [
            'value' => 'default',
            'label' => __('Default'),
            'disabled' => true,
        ],
    ];
}

Release note

No response

[m2-assistant]

Hi @rybkinevg. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[rybkinevg]

@magento I am working on this

[m2-assistant]

Hi @engcom-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.