[Backport to release/10.3] Fix: respect theme support to control legacy script loading for block themes #61837
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is a cherry-pick of #61205 to
release/10.3.Original PR Description
Submission Review Guidelines:
Changes proposed in this Pull Request:
(For Bug Fixes) Bug introduced in PR #60223
Since #60223, We always load legacy single product assets when using the Classic Template block. This is our effort to improve the frontend performance of the single product page for block themes (by not loading legacy assets by default).
However, this poses an issue for users of the Classic Template block, as they can not opt out of legacy gallery assets anymore using
remove_theme_support. To resolve this, this PR follows the @Aljullu brilliant suggestion to let us respect theme supports on block themes.How to test the changes in this Pull Request:
Using the WooCommerce Testing Instructions Guide, include your detailed testing instructions: