WooCommerce Brands CSS File Unconditionally Enqueued on All Pages
Summary:
The WooCommerce plugin incorrectly enqueues a CSS file for its 'Brands' feature on every page of a WordPress site, regardless of whether the feature is being used. The 'brands.css' file is loaded on the frontend even when no brands are configured or displayed, leading to unnecessary HTTP requests and a slight performance impact.
This issue occurs because the stylesheet is registered and enqueued without any conditional logic to check if the brands functionality is active or needed on the current page. The bug is present in a default WordPress environment with only WooCommerce active and a default theme, confirming it is a core plugin issue.
The impact is that all sites running WooCommerce, even those not utilizing the brands feature, incur the overhead of loading this extraneous CSS file, which violates best practices for asset loading.
How to Replicate:
- Install and activate the WooCommerce plugin on a WordPress site.
- Ensure no brands are configured and the feature is not in use.
- Visit any page on the frontend of the site (e.g., homepage, post, product page).
- Open the browser's developer tools and navigate to the 'Network' tab.
- Reload the page and filter the loaded resources by 'brands.css'.
- Observe that the 'brands.css' file is present in the list of loaded resources.