Build system doesn't handle byte order markers when combining CSS files

[Scott Hunter]

When building and combining @imported CSS files, the build system does not strip out UTF-8 byte order marks (BOMs) when inlining files. In the resulting CSS file, the raw BOM bytes (EFBBBF) appear directly in the middle of the combined file, which alters or invalidates the first declaration in the included file.

[Rawld Gill]

In [29277]:

remove BOM in flattened CSS; fixes #15236; !strict

[bill]

Hmm, seems like if you read in the file as text it should be stripped automatically, maybe the problem is that you are using importModule.rawText instead of importModule.text. (I also wonder if that's causing other problems like CR-LF issues on Windows.)

[Rawld Gill]

Replying to bill:

Hmm, seems like if you read in the file as text it should be stripped automatically,

You would think. Unfortunately, this seems to be a sporadic problem with node.

maybe the problem is that you are using importModule.rawText instead of importModule.text. (I also wonder if that's causing other problems like CR-LF issues on Windows.)

I don't understand your observation: when a file is flattened, the original text is copied to rawText and text is set to the processed version.

[bill]

Oh OK, I was guessing (apparently incorrectly) that rawText and text were creating by the Node file library, not by your code.