By design.Is this by design or a bug?
You must explicitly save/accept.also after I log in the cookie notice persists.
Ya, that was my first thought as well. I suppose one could completely revamp the JavaScript loading system or something where you can flag scripts at setting third-party cookies, then let some code logic sort out if you want to load it based on the user's settings. But that seems like a pretty major (breaking) change for a patch version like 2.2.12 (not even a minor version like 2.3).I wonder how third-party cookies will be implemented and how blocking them will work. We'll see soon.
Because certain parts of a page load based on the cookie settings (for example Google Analytics). Say you were going from allowing it to not allowing it, you need to refresh the page for that to take action because it was already loaded (need a new page load to not load it). Once it's loaded it might still send things happening on the page itself after you've made a new selection.Why saving cookies selection refreshes the page?![]()
You are able to change it after the fact on any page view. It's not just the initial page view that dialogs is for/works on. Look at the bottom left of all pages here now... there's a "Cookies" link that brings up the dialog. You would have all sorts of issues if you blocked all cookies by default and made the selection only available on the first page view.In my understanding, before selecting “allow” for Google Analytics, it don’t should be injected in page. So it looks… very crutchly.
Nope... the version that is running here appears to be in the 2.2.x branch. It has features slated for 2.2.12 (like Turnstile), and missing things slated for 2.3 (like WebP support).Did I just see signs of smoke of XF 2.3?
We use essential cookies to make this site work, and optional cookies to enhance your experience.