Closed (fixed)
Project:
EU Cookie Compliance (GDPR Compliance)
Version:
8.x-1.23
Component:
Documentation
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
3 Oct 2022 at 09:02 UTC
Updated:
19 Oct 2022 at 17:49 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
svenryen commentedThe withdraw button goes on a withdraw banner (after having consented), and reject all button goes on the first banner, where you can close the banner and reject all cookies by clicking it.
Did that clear up things?
Comment #3
lucky723 commentedBut both have the same role : uncheck all optional cookies, right ?
Comment #4
svenryen commentedThere are two buttons in order to give the user clearer message;
Comment #5
svenryen commentedNow that you mention it, it makes little sense to have both buttons available at the same time.
The plan was to have a Withdraw button after consent has been given, so we should look into hiding the Reject button if Withdraw is there.
Having a Withdraw button adds some value, as it signals to the user that consent has previously been given and can be revoked.
Also "Withdraw consent" sets the cookie value to NULL, whereas "Reject all" sets the cookie value to 2.
Think of "Withdraw consent" as a reset button. It sets the consent state back to the value it had when the visitor first entered the site.
Comment #6
svenryen commentedComment #8
svenryen commented