Currently, the posthog cookie gets set again after manually removing both the posthog cookie and the cookiesjsr cookie and reloading the page. This shouldn't be the case, as by default, consent is denied.
Simply denying the cookie, the posthog cookie on the initial site visit, will block the cookie as expected.
After some investigation of @anybody and I, this should be caused by some initialization from the cdn posthog.js or a chrome related bug. We should try to reproduce this with firefox as well.
Find a solution.
Active
1.0
Code (posthog_cookies)
Ok let's tackle this one next week together with the tests.
No I don't think so. We already spent a lot of time in this.
As the summary says, this is probably related to library itself. Let's keep this active, but not active active.