Firefox not always saving consent
-
Hi,
on my page I with Woocommerce I use
wc-ajax=get_refreshed_fragments.This causes the consent json-call to take longer as it has to wait for the server to answer that wc-ajax call – as I have a slow local server up to 9000ms.
During investigating this I found out, that this causes the consent json-call of your plugin to wait and as the server is slow, the json-call itself takes up to 9000ms as well.
This is no issue if I stay long enough on the page, but if I change the page during that load time Firefox and Chrome start to behave differently.
While Chrome is finishing the consent json-call before changing to the next page Firefox is aborting the json-call and changing the page immediately – and not saving the consent thus.
So my question is, is this browser related or is it possible to have Firefox reacting the same way as Chrome and finishing the call before changing pages.
Its better to have one time a slower page than having the popup appear on every page again.
-
Hi, I close this issue as it is mostly related to my slow server.
But maybe it is possible to have a spinning wheel or something else after closing the cookie banner until the consent is saved – this would not affect fast connections, but indicate on slow servers that something is happening.
As it would run only one time – while saving the consent – it would not affect overall performance.
This would avoid the issue with the cookie banner popping up multiple times as the consent is not properly saved.
- The topic ‘Firefox not always saving consent’ is closed to new replies.
