All Submissions:

• Have you followed the WooCommerce Contributing guideline?
• Does your code follow the WordPress' coding standards?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Changes proposed in this Pull Request:

wc-cart-fragments allows statically rendered elements to be updated when a product is added to the cart. It does this with an additional AJAX call to the get_refreshed_fragments endpoint. This does create a performance issue where extra requests are made to the server to support it.

There are several articles on the web detailing how this is a problem and recommending to dequeue it [1], as well as workarounds which replace the functionality entirely [2].

Given that the main consumer of this functionality is the Cart Widget, and that the Cart Widget is being superseded by the Mini Cart Block, I propose we remove this from the global enqueues and move it to the Cart Widget only, so the widget can continue to use fragments, but other pages in the store do not need to load the script.

This was proposed here: woocommerce/woocommerce-blocks#7168

We plan on removing support for fragments in WooCommerce Blocks, and potentially dequeuing it completely in the interim.

• [1] https://wpengine.com/support/how-to-disable-cart-fragments-for-woocommerce/

• [2] https://wpengine.com/blog/solving-cart-fragment-dilemma-introducing-live-cart/

• This PR is a very minor change/addition and does not require testing instructions (if checked you can ignore/remove the next section).

How to test the changes in this Pull Request:

1. With the patch applied, and with no widgets setup, visit the shop page.
2. View the page source and confirm the cart-fragments.js script is not loaded.
3. Add the cart widget to a sidebar in the theme.
4. View the page source and confirm the cart-fragments.js script is loaded.

Other information:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your changes, as applicable?
• Have you created a changelog file for each project being changed, ie pnpm --filter=<project> changelog add?

FOR PR REVIEWER ONLY:

• I have reviewed that everything is sanitized/escaped appropriately for any SQL or XSS injection possibilities. I made sure Linting is not ignored or disabled.