Depending from multiselect in backend is broken

[bjornsnoen]

Preconditions (*)

1. Magento ^2.2 (and probably earlier)

Steps to reproduce (*)

1. Create a module with an etc/adminhtml/system.xml file

<?xml version="1.0" encoding="UTF-8"?>
<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:module:Magento_Config:etc/system_file.xsd">
    <system>
        <section id="general">
            <group id="test" showInStore="1" showInWebsite="1" showInDefault="1" type="text" sortOrder="999">
                <label>Proof of concept</label>
                <field id="multiselect_id" translate="label" type="multiselect" sortOrder="2" showInDefault="1" showInWebsite="1" showInStore="0" canRestore="1">
                    <label>multiselect_id</label>
                    <source_model>Magento\Sales\Model\Config\Source\Order\Status</source_model>
                </field>
                <field id="brand_attribute" type="text" sortOrder="3" showInStore="1" showInWebsite="1" showInDefault="1" translate="label,comment">
                    <label>Brand attribute</label>
                    <depends>
                        <field id="multiselect_id" separator=",">processing</field>
                    </depends>
                </field>
            </group>
        </section>
    </system>
</config>

2. Select all the options

Expected result (*)

1. The depending field should appear and become editable

Actual result (*)

1. The field remains hidden until one unselects all options preceding the one one depends from
   

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @bjornsnoen. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• 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, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[ihorvansach]

@bjornsnoen, thank you for your report.

I've made tests on latest Magento2.3.5p2 and 2.4.0 and was not able to reproduce the issue.

I used this code for testing

<field id="multiselect_id" translate="label" type="multiselect" sortOrder="2" showInDefault="1" showInWebsite="1" showInStore="0" canRestore="1">
    <label>multiselect_id</label>
    <source_model>Magento\Sales\Model\Config\Source\Order\Status</source_model>
</field>

<field id="brand_attribute" type="text" sortOrder="3" showInStore="1" showInWebsite="1" showInDefault="1" translate="label,comment">
    <label>Brand attribute</label>
    <depends>
        <field id="multiselect_id" separator=",">processing</field>
     </depends>
</field>

@bjornsnoen, please make sure that you can reproduce this issue on the latest Magento version. Let me know if I missed something.

[bjornsnoen]

Hm, I was reproducing it on 2.3.4-p2, and since the broken js is still there in 2.4 I was sure it would still be broken. I guess the functionality may have been amended elsewhere. I'll see if my module will reproduce it on 2.3.5-p2, if it doesn't I'll happily close :)

[koushikch7]

@magento give me 2.3-develop instance

[magento-deployment-service]

Hi @koushikch7. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @koushikch7, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.