Minicart cannot be used twice in the same page

[ioweb-gr]

Summary

The minicart element can't be used twice in the same page due to harcoded bindings.

For example in Magento_Checkout::js/view/minicart.js you can see that it will hook into [data-block="minicart"] without any possibility to override this.

In some other cases when you have a header bar that's displayed on desktop and a different one tht's displayed on mobile you may still experience the issue.

Basically we're only left with trying to move around the minicart using jquery instead of being able to toggle it's visibility per case.

When using two of them, one of them won't be able to display it's dropdown.

Unless I'm missing in which case please correct me, this looks like something that wasn't intended.

Examples

Here's a sample layout that's not really possible without jQuery due to the limitation of the minicart

In this case randomly one of the two minicarts won't display it's dropdown.

Proposed solution

The binding element should be decided by the config of the ui component as in other components.

From minicart.phtml you see that the binding is on element [data-block='minicart']

    <script type="text/x-magento-init">
    {
        "[data-block='minicart']": {
            "Magento_Ui/js/core/app": <?= /* @noEscape */ $block->getJsLayout() ?>
        },
        "*": {
            "Magento_Ui/js/block-loader": "<?= $block->escapeJs(
                $block->escapeUrl($block->getViewFileUrl('images/loader-1.gif'))
            ) ?>"
        }
    }
    </script>

In the config of the ui compoment the binding element selector should be possible to configure so that we can use unique identifiers.

An alternative solution would be when there are multiple elements with the same functionality

[data-block='minicart']

It should bind to both of them properly and make sure the dropdown works.

Release note

No response

Triage and priority

• [ ] 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[bot]]

Hi @ioweb-gr. 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. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• 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. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: 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.

[ananth-iyer]

@ioweb-gr Did you added new div with [data-block="minicart"]

[ioweb-gr]

@ananth-iyer In the html there are two instances of [data-block="minicart"] one for each minicart block

This is an example http://polr.ioweb.gr/PQLCC

[m2-assistant[bot]]

Hi @engcom-November. 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: :point_down:

• [ ] 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

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - 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.

[engcom-November]

Hello @ioweb-gr,

Thank you for the report and collaboration!

Verified this on 2.4-develop. Added minicart in the footer, when clicking the minicart it opens up at the default location. Please take a look at the screencast:

Hence Confirming this issue.

Thank you.

[github-jira-sync-bot]

:white_check_mark: Jira issue https://jira.corp.adobe.com/browse/AC-12579 is successfully created for this GitHub issue.

[m2-assistant[bot]]

:white_check_mark: Confirmed by @engcom-November. Thank you for verifying the issue.
Issue Available: @engcom-November, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[ioweb-gr]

Thank you :) any idea for a quick patch for this? It's a really pestering bug