“Select Shipping Method” page of Multishipping Checkout is corrupted if a Customer use “go back” browser button to return to the page

[magento-engcom-team]

Preconditions:

• Magento EE 2.3.5-p2, EE 2.4.0, EE 2.4.0-p1, EE 2.4.1-alpha3{color} is installed, should be actule for CE
• A Simple product is created
• A Customer account with two shipping addresses is created
• Check / Money order Payment method is configured
• Flat Rate shipping method is configured

Steps to Reproduce:

• Go to the Storefront as the created Customer
• Add the created Product (2pcs) to the Shopping Cart
• Open the mini-cart
• Click the {color:#0747a6}“View and Edit Cart”{color} link
• Click the “{color:#0747a6}Check Out with Multiple Addresses”{color} link
• Select shipping addresses
• Click the “Go to Shipping Information” button
• Select Flat Rate shipping method
• Click the “Continue to Billing Information” button
• Click the "Add or remove gift cards" link on the “Billing Information” page
• Wait until the “Shopping Cart” page is loaded completely
• Click the “go back” browser button (left arrow)
• Click the {color:#0747a6}”Back to Shipping Information” link on the “Billing Information” page

Expected results:

• “Select Shipping Method” page should be loaded
• The page should not be corrupted

Actual results:

(/) “Select Shipping Method” page is loaded
(x) The page is corrupted 

[magento-engcom-team]

The issue was exported from the internal JIRA. The link to the original JIRA issue: https://jira.corp.magento.com/browse/MC-36425

[m2-assistant]

Hi @magento-engcom-team. 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

[magento-engcom-team]

✅ Confirmed by @magento-engcom-team
Thank you for verifying the issue. Based on the provided information internal tickets MC-36425 were created

Issue Available: @magento-engcom-team, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[m2-assistant]

Hi @engcom-Kilo. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.
• 2. 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!
• 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[magento-engcom-team]

Hi @magento-engcom-team, @engcom-Kilo.

Thank you for your report and collaboration!

The related internal Jira ticket MC-36425 was closed as Fixed.

The fix will be available with the upcoming 2.4.3 release.