Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.If a css file encoded in UTF8 with BOM is part of an aggregate, that file and all the CSS files that are aggregated after that one get "lost" because at some point file encodings are missused and the Byte Order Mark becomes a bad character inside the final CSS file.
Still trying to figure out what the best solution is (besides removing BOM from the file).
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | advagg-2576381-7-fix-bom-js-css.patch | 3.52 KB | mikeytown2 |
| #5 | advagg-2576381-5-fix-bom-js-css.patch | 3.52 KB | mikeytown2 |
| #3 | 2576381-fix-BOM-compatibilty.patch | 2.37 KB | david_garcia |
Comments
Comment #2
david_garcia CreditAttribution: david_garcia commentedThis is how they approached it in D8:
https://www.drupal.org/files/issues/css_files_encoded_in-1833356-33.patch
Comment #3
david_garcia CreditAttribution: david_garcia commentedImplement something similar to what's in D8.
Comment #4
mikeytown2 CreditAttribution: mikeytown2 commentedLink to the issue: #1833356: CSS files encoded in UTF-8 with BOM break the design when enabling CSS aggregation
Comment #5
mikeytown2 CreditAttribution: mikeytown2 commentedLooked at what was added in D8 and made sure the code closely matches the flow.
Comment #7
mikeytown2 CreditAttribution: mikeytown2 commentedComment #9
mikeytown2 CreditAttribution: mikeytown2 commented#7 has been committed
Comment #10
david_garcia CreditAttribution: david_garcia commentedThaaaaaanks!