Browser: Chrome 110 OS: Windows URL: Link to a page that illustrates this issue Video: Short screen recording that illustrates this issue (free tool: jam.dev)
Hi bricks team,
In Bricks, when we enable a filter, other filters (Checkbox, radio, pagination and active filters elements) are disabled for a while because bricks adds the brx-filter-disabled class. This is detrimental to the user interface because it prevents users from quickly filtering through the filters they want. They have to wait for brx-filter-disabled to be removed before they can enable the next filter.
But this is not the case in the 2025 theme and the brx-filter-disabled class is never added. This greatly improves the speed of the workflow. Please see the gif below.
Not so sure how you test the Bricks filter feature in 2025 WP theme while Bricks theme is not activated.
First I tested the Bricks filters, then I activated the 2025 theme and used the WooCommerce filter block. What you saw in the GIF were native WooCommerce filters.
The disabled class is to avoid the user interupt the current AJAX request.
Sorry, but I didn’t understand. When this class is added, it happens to cause a break in the application of filters. So unlike native WooCommerce filters, we can’t activate filters quickly. We have to activate one filter first, add and remove the class before we can activate the next filter. Am I missing something?
I hope this report has not upset you. You are undoubtedly the best coders in the world. I may be wrong, but adding the “brx-filter-disabled” class doesn’t really make sense. Let me give you another example.
If you look at wp grid builder filters and even jet smart filters, the reset filter has a class of “disabled” when no filter is active. This helps to customize the style of the button when no filter is active. But in Bricks this class is only added to the button for a moment and then removed.
Another example of filters where the “disabled class” is not added when activating a filter.
