Configurable Options Not Working After Moving .price-box Outside of .product-info-main in Magento 2.4.7

[Zwernemann]

Preconditions and environment

Magento Version: 2.4.7
Customizations: Modified catalog_product_view.xml layout file in Magento_Theme/Magento_Catalog/layout

Steps to reproduce

1. Upgrade Magento to version 2.4.7.
2. Modify the catalog_product_view.xml layout file by adding the following code (with this the price element will be added to a sticky footer)

3. Ensure that the .price-box element is moved outside of the .product-info-main element and placed inside a sticky footer element.
4. Attempt to select configurable options on the product page.

Expected result

• Configurable options should be selectable and update the product price correctly, even after moving the .price-box outside of the .product-info-main element.
  

Actual result

• Configurable options do not work correctly. The dropdown for configurable options remains empty.

• This issue occurs due to the change in priceHolderSelector, which was previously .price-box and is now .product-info-main [data-role=priceBox].

Additional information

• The issue did not exist in Magento versions prior to 2.4.7. The change in /web/js/configurable.js priceHolderSelector seems to have affected installations where .price-box is moved outside of .product-info-main.
• I was able to resolve the issue temporarily by reverting to the previous version of /web/js/configurable.js.
• I added a comment at da20c4e that describes the error.

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]

Hi @Zwernemann. 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.
⚠️ 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.

[m2-assistant]

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

  - 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-Delta]

Hi @Zwernemann ,

Thanks for your reporting and collaboration.
We have re-verified the issue in Latest 2.4-develop instance , but we are unable to reproduce the issue. Kindly refer the screenshots.

Steps to reproduce

1. Modify the catalog_product_view.xml layout file by adding the following code (with this the price element will be added to a sticky footer)
   
2. Attempt to select configurable options on the product page.
   Observe, user is able to view configurable options

Can you please re-verify and confirm if you are still facing the issue.
Thanks.

[Zwernemann]

Hi @engcom-Delta ,

in my case the .price-box is outside of the .product-info-main.

The .product-info-main Class is located above in my case:

then configurable.js stops working, because the normalPriceLabelSelector is as follows:

In former release the priceHolderSelector in configurable.js was directly ".price-box".

See my comment in: here

[engcom-Delta]

Hi @engcom-Hotel ,

Assigning it to you as ticket is marked as dev experience.

Thanks.