Sure it is a thing but JavaScript on that domain can access it either injected or provided by the site. This is quite risky. Cookies can be http only so that client code cant access it.
Because we were talking about how to save that information without using cookies. Setting a cookie would break the one thing that the conversation was about, wouldn’t it?
If we’re in a fun conversation about how to enter your home without using the door, would you be the one saying “I have an idea, I have an idea: use the door”?
It was clearly a reference to the so called ‘cookie laws’ requiring permission for tracking cookies. However, cookies that are not for tracking purposes do not require any form of consent.
Sure it is a thing but JavaScript on that domain can access it either injected or provided by the site. This is quite risky. Cookies can be http only so that client code cant access it.
How is storing
hideCookieBanner: falseon local storage risky?What would the benefit of storing that in local storage?
Remembering that the user asked to not see that banner again.
Why not just set a cookie?
Because we were talking about how to save that information without using cookies. Setting a cookie would break the one thing that the conversation was about, wouldn’t it?
If we’re in a fun conversation about how to enter your home without using the door, would you be the one saying “I have an idea, I have an idea: use the door”?
It was clearly a reference to the so called ‘cookie laws’ requiring permission for tracking cookies. However, cookies that are not for tracking purposes do not require any form of consent.