- Issue created by @florianboehme
- 🇩🇪Germany jurgenhaas Gottmadingen
We've implemented Klaro this way in Drupal CMS intentionally. We don't want to disturb the user experience if it's not required. When it comes to the link in the footer, in Drupal CMS that's not enabled by default, only if at least 1 requirement has been identified. If that requirement disappears later on, then the link should also be disabled again. We haven't thought, this should be automated too, as we didn't think that something like that would be built back. And also, it would be difficult to determine as that would have to check for every config change on a Drupal site potentially, that's simply too much, I guess.
- 🇩🇪Germany florianboehme Koblenz, 🇩🇪
I get the intention behind this. But wouldn’t it be an idea to give site builders the option to enable it manually? Technically, it wouldn’t need to check every single config change, right? (Apologies if I’m missing something here – not my strongest area 😅).
It’s really just about displaying the banner even if no new service has been added. I can already hear the data protection officers complaining: “Where’s the cookie banner informing about functional cookies?” 😆
What do you think?
- 🇩🇪Germany jurgenhaas Gottmadingen
It’s really just about displaying the banner even if no new service has been added. I can already hear the data protection officers complaining: “Where’s the cookie banner informing about functional cookies?” 😆
To show a dialog where the user can't do anything? Do we want to worsen the user experience when visiting our sites? I know, the cookie banners have been (and still are) everywhere since 2018. But that was just wrong and made the whole world hate GDPR and privacy in general. We should sell this as an improvement: we no longer disturb the visitors, unless we have to.
- 🇩🇪Germany florianboehme Koblenz, 🇩🇪
Totally makes sense and checks out. I’m with you on that. Got it! Let’s make the world of annoying cookie banners a better place.
- 🇩🇪Germany jan kellermann
Thank your for discussing.
Do you have some additions for the README or documentation?
Else I would like to close this issue.
Automatically closed - issue fixed for 2 weeks with no activity.