Alex

Hi,
Thanks for detailed explanation, I know the difference between scripts and cookies, and how it’s created, but I still don’t think you understood the issue – it’s not a technical (adding “if” condition), but logical issue: what’s the reason to delete all cookies when a user given the explicit consent for all cookies?

The only thing that our plugin can control (if it’s setup properly) is which scripts will be executed when user gives consent.

Therefore, if user changes their preferences, we have to delete all cookies and reload the page so that only the scripts that user consented to can be activated (and therefore store cookies).

It’s true, that you may not know which cookies are which, when a user partially agreed or rejected, and the full delete is needed then. But why it’s needed to deleted all when a user explicitly agreed to all (by clicking “Accept” / “Enabled All”)? All means all – no scripts will be removed / skipped, all the scripts will be loaded / activated, and all the same cookies will be re-installed, except missing cookies that were previously installed by a condition (by UTMs, ad click trackers – ruining ad conversions etc) or created dynamically by user’s actions on a site etc. Just doesn’t make any sense from the user side – I’m agreeing to all cookies, but the plugin deleting all cookies first.

window.addEventListener('DOMContentLoaded', function() {
	console.log('vanilla - DOMContentLoaded');
});
$(function(){
	console.log('jquery - DOM loaded');
});

jQuery v1/v2 will give us:

jquery - DOM loaded
vanilla - DOMContentLoaded

jQuery v3 will give us:

vanilla - DOMContentLoaded
jquery - DOM loaded