3 ms·
One simple factor could be "does the user have a password (or WebAuthN credential) stored for this web site". Otherwise have a way for the web site to trigger
by tgsovlerkhgsel 6y ago
One simple factor could be "does the user have a password (or WebAuthN credential) stored for this web site".
Otherwise have a way for the web site to trigger a browser-controled consent UI. This would be a one-shot thing and clicking "no" would trigger a spam signal. Too many of these and the web site loses its "ask for cookies" permission.
Cookies for anything not trusted have a lifetime of "until the tab is closed".
- qwerty456127 6y ago> This would be a one-shot thing and clicking "no" would trigger a spam signal. Too many of these and the web site loses its "ask for cookies" permission. Don't be too rough on them. You should look for a viable and sustainable solution, not a radical GtFO doomed to end here. > Cookies for anything not trusted have a lifetime of "until the tab is closed". "until the tab is closed" policy isn't convenient even for the user. I tried it and reverted to "until the browser is closed" quickly.