🇨🇦Canada @jmoruzi

The following applies to both 2.0.8 (patched or un-patched) and 3.0.0-beta1

Neither of these patches has any affect for me. I tested each patch individually on v2.0.8, as well as together, and in all 3 situations I see the same behaviour as if no patches are installed. In all browsers facets work as expected as long as you do not touch the back button.

There is no change in behaviour in Firefox, and there are issues in Chromium browsers as well.

In Firefox:

1. I select a facet and results are filtered properly.
2. Select a second facet and results are filtered properly.
3. Click the back button, and the previous page loads with the results from the first facet, which is the desired behaviour, but both facets are still selected, and disabled
4. Click the back button again, and only the first facet is selected, but disabled

Even if I click the back button again to go to the previous page that has filtered results, and then select the forward button to go to the page with the faceted results, the facets are still disabled until I reload the page.

Chrome, Edge and Brave:

There are no issues with the facets being disabled, but they are not activated properly once you use the back button.

1. Select a facet and results are filtered
2. Select a second facet, and results are filtered
3. Uncheck the first facet and results are filtered properly
4. Click the back button, you're taken back to the previous page, but the facet that was deselected in step 3 is still unchecked, so there is a disconnect between the selected facets and the results shown on the page. You're seeing the result of facet 1 and 2 being selected, but only facet 2 is checked.
5. Uncheck facet 2, the page reloads, and now the first facet is checked. The results on the page are filtered properly.
6. Click the back button. No facets are checked, but the results are filtered on the first and second facets.

This may be the same behaviour you would see in Firefox, but since the facets are disabled after clicking the back button there's no way to know.

Thank you, the error is gone and the images are displaying correctly now.

jmoruzi → created an issue.

I'm getting the same error, "Uncaught TypeError: $(...).once is not a function" with the latest version and D10.2.4.

Can you clarify the suggestion above where you say "As well as point the core/once library in cocoen_beforeafter.libraries.yml" please. What do I need to change/add in the libraries file?

The previous version of this module worked great on D9 and I'd like to keep it in D10 but right now it's not working.

Thanks.

jmoruzi → created an issue.

jmoruzi → created an issue.