Add a clearly labelled "decline" button to the default themes about extension-cookieman

Our lawyer has described this problem in the same way. We have already renamed the button to "Reject", but unfortunately this has the effect that if you change the entries or edit them afterwards, you will also have the "Reject" button, although you would prefer the "Save" button at this point.

[jonaseberle]

Hi Nico,

the "reject" button should have data-cookieman-accept-none data-cooieman-save. I suggest to add this button instead of renaming the "save" button.

What I am planning for the default templates would be a logic that shows/hides buttons depending on the current selection.

Do you have a suggestion when each button should be shown?

Hello,

thanks for the tip with data-cookieman-accept-none.

According to our lawyer, the combination of the save button and expandable settings is problematic. In general it should not be easier to accept all cookies than to reject all unnecessary ones. I know that all non-essential cookies are already deselected in the settings, the customer must first open the settings to check this. As I am writing I am just realizing that it might be a good idea to keep the settings always open.

What would it be like if you made it basically configurable, which button is shown when? There are two states if I have seen it correctly: The first state is when a visitor comes to a website and doesn't have a "CookieConsent" cookie, and the second state is when he already has one and wants to change his decision. In both cases you can decide for yourself if you want to have a save or reject button. It's probably very hard to make a suggestion because the whole cookie thing is legally controversial. Every lawyer has his own interpretation as the relevant laws do not really exist as far as I know.

[jonaseberle]

As a first step we could focus on being legally compliant and have 3 buttons:
reject all / save / accept all

I think having the "reject all" (or "decline all" - I'll ask for native speakers in TYPO3 slack #gdpr) is the current requirement. Yet even big cookie consent providers did not implement that yet (E.g. https://borlabs.io/borlabs-cookie/ https://www.cookiebot.com/). https://cookiefirst.com/ on the other hand has it.

Then we could focus on UX improvements.
The simplest improvement would be to only show the "save" button if the selection has changed. We could make it configurable by means of data-cookieman-* attributes.

[jonaseberle]

I have implemented "Deny all" into the default templates now.

I show the "save" button after "settings" have been opened.

That's not the most sophisticated UX, but I was lazy right now... Please reopen the issue if that matters.