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).

Comments

david_garcia created an issue. See original summary.

david_garcia’s picture

david_garcia’s picture

Status: Active » Needs review
StatusFileSize
new2.37 KB

Implement something similar to what's in D8.

mikeytown2’s picture

StatusFileSize
new3.52 KB

Looked at what was added in D8 and made sure the code closely matches the flow.

Status: Needs review » Needs work

The last submitted patch, 5: advagg-2576381-5-fix-bom-js-css.patch, failed testing.

mikeytown2’s picture

Status: Needs work » Needs review
StatusFileSize
new3.52 KB

mikeytown2’s picture

Status: Needs review » Fixed

#7 has been committed

david_garcia’s picture

Thaaaaaanks!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.