When using Cookiebot with auto blocking enabled javascript can break in certain situations. When Cookiebot scans a javascript file that may potentially set a cookie the file will be blocked. This is especially a problem when used together with JS aggregation.
While autoblocking is still a very useful feature it shouldn't break javascript, even if it can potentially set cookies.
The keep autoblocking enabled I'm proposing to exclude all javascript generated by Drupal from being tracked. There are more advanced solutions like https://www.drupal.org/project/cookie_blocking_libraries → that allow you to configure every single library, but this doesn't work with aggregation.
Active
1.0
Code
This patch will exclude processed / aggregated JS files from auto blocking.
If a script does not to be blocked automatically this implies that script or library should be excluded from aggregation.