1. Cookie policy management should be done at browser level with using standard HTML/JS constructs. Instead, everyone nowadays is doing it by adding custom HTML

1. Cookie policy management should be done at browser level with using standard HTML/JS constructs. Instead, everyone nowadays is doing it by adding custom HTML to their own pages to handle the panel/popup logic: they're doing it wrong, because it makes it much harder to detect which part of the page hosts the cookie settings panel. 2. Also, many of those panels have "Accept all" as a default option. Many make it purposely hard to disable some trackers without going deep down into crowded cookies preference pages. This is also the wrong way of complying to GDPR, and the sites that do it must be appropriately punished. The default should be "Deny all except for non-third-party functional cookies". 3. In the meantime, NoScript helps blocking some of that crap. If you never whitelist domains like cookielaw.com you're unlikely to see many of them.