v1.9.2 – Apply button changes causing problems

Hi there,

We’re seeing some issues with the ‘Apply button mode’ introduced in Filter Everything 1.9.2.
Reverting to 1.9.1 removes the problem.

Environment (summary)

• WordPress + WooCommerce product archives with AJAX filtering enabled
• LiteSpeed Cache with image lazy loading enabled
• Apply button mode in use (filters applied after user action)

Symptoms

1. The first filter application behaves as expected (e.g. narrow to a product category).
2. When a second filter is applied (e.g. an additional taxonomy/meta/date filter such as a release month), the product loop updates but product images do not appear — we see empty/grey placeholder areas where thumbnails should be.
3. Opening DevTools (or anything that forces a strong resize/reflow) often causes images to appear, which points to layout / intersection / scroll timing, not missing HTML.
4. Disabling LiteSpeed’s image lazy load makes the issue go away while staying on 1.9.2.

So the failure mode is Filter Everything 1.9.2 + AJAX-injected product HTML + LiteSpeed’s lazy-load implementation. It does not occur on 1.9.1 under the same LiteSpeed and site configuration.

Likely cause:

Your 1.9.2 changelog includes: “Improved the Apply and Reset buttons in Apply Button mode. They are now floating for better usability.”

In 1.9.2 we see new frontend behaviour that is not present in 1.9.1, including:

• Markup related to sticky / floating apply controls (e.g. .wpc-sticky-buttons, placeholders)
• New JavaScript that attaches window scroll handling, measures layout (getBoundingClientRect, offsets), inserts placeholders, and applies fixed positioning — and hooks this into the AJAX success path around the same time the posts container HTML is replaced and events such as <code class=””>scroll / <code class=””>resize are fired.

LiteSpeed’s lazy loader is sensitive to DOM replacement + scroll/layout after load. The new floating-apply flow appears to interfere with that pipeline so below-the-fold or lazily processed images in the updated grid never get processed until something forces a reflow (e.g. DevTools).

Workaround we use today

• Stay on 1.9.1, or
• Keep 1.9.2 and exclude WooCommerce loop images from LiteSpeed lazy load (or disable its image lazy load), which is a site-wide tradeoff.

Can you add an option to disable sticky / floating behaviour please?
The new sticky / floating behaviour forces the buttons above our open / close buttons as well as breaking lazy load, so having the option to use the legacy setting (1.9.1) would be an ideal fix.
Currently with 1.9.2 active and lazy load disabled, we still need to apply the following custom css so the buttons display correctly:

/* Apply Button mode customization */
.wpc-sticky-buttons {
padding: 0 !important;
z-index: unset !important;
border: none !important;
position: relative !important;
top: auto !important;
bottom: auto !important;
}

Thank you for your help!