Aggregated files blocked by Adblock Plus Chrome Extension

Created on 18 May 2016, almost 9 years ago
Updated 20 August 2023, over 1 year ago

The default filter list included with Chrome extension Adblock Plus is EasyList. https://easylist.github.io/easylist/easylist.txt

It contains the following filters:

-ad03.
-ad1.
-ad2.
-ad3.
-ad4.
-ad5.

When using a fully updated version of this filter list, aggregated CSS files that happen to end in any of these combinations are blocked.

drupal_build_css_cache() currently prepends CSS files with 'css_' to prevent them from being blocked accidentally. We may need to add a similar suffix on automatically generated CSS files.

πŸ“Œ Task
Status

Active

Version

11.0 πŸ”₯

Component
Asset libraryΒ  β†’

Last updated 3 days ago

No maintainer
Created by

πŸ‡ΊπŸ‡ΈUnited States jastraat

Live updates comments and jobs are added and updated live.
  • Needs tests

    The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • The Needs Review Queue Bot β†’ tested this issue. It either no longer applies to Drupal core, or fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".

    Apart from a re-roll or rebase, this issue may need more work to address feedback in the issue or MR comments. To progress an issue, incorporate this feedback as part of the process of updating the issue. This helps other contributors to know what is outstanding.

    Consult the Drupal Contributor Guide β†’ to find step-by-step guides for working with issues.

  • πŸ‡¬πŸ‡§United Kingdom catch

    After πŸ› Stampedes and cold cache performance issues with css/js aggregation Fixed (in 10.1.x) AssetDumper::dump() is no longer used in core, except in two deprecated classes which are no longer used.

    That means this issue should be 'fixed' apart from the code still being there. I've opened πŸ“Œ Deprecate AssetDumper::dump() Active to deprecate the methods.

    The new URLs shouldn't have this problem since any hashes are only in query arguments not the main filename, although not closing this out just yet because it would still be feasible to fix this for 10.0.x and 9.5.x, and it might be worth a second opinion on whether the new URLs are adblocker proof.

  • Status changed to Active over 1 year ago
  • πŸ‡¬πŸ‡§United Kingdom catch

    #25 is wrong, the filenames still have hashes in 10.1.x

    However I have no idea how we can prevent that string from appearing in the filename - the hash is meaningful.

    What about adding the suffix to the filename for some filters? Other ones should probably have bug reports opened against them.

Production build 0.71.5 2024