Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

CSS files with UTF-8 BOM triggers CSS errors

See original GitHub issue

I noticed that if a CSS file has a UTF-8 BOM then HtmlUnit seems to not like it - It throws a CSS error:

com.gargoylesoftware.htmlunit.DefaultCssErrorHandler error
WARNING: CSS error: 'http://localhost:59425/cargo-daemon-webapp/cargo.css' [38:1] Error in style rule. (Invalid token "body". Was expecting one of: <S>, <LBRACE>, <COMMA>.)

The UTF-8 BOM doesn’t seem to “bother” Web browsers, could HtmlUnit also be updated to behave similarly?

Issue Analytics

State:
Created 3 years ago
Comments:7 (5 by maintainers)

Top GitHub Comments

1reaction

rbricommented, Jul 17, 2020

Ok, hopefully i have covered the most important cases. Please check twitter for a new snapshot build.

Many thanks for reporting this.

1reaction

rbricommented, Jul 14, 2020

I think it could be worthwhile to enable HtmlUnit to work with UTF-8 BOMed files, as Windows tends to save with a BOM and browsers seem to be fine with it.

Yes this is the plan - removing the BOM is not so tricky (i already did it at some other places) but it will require some time to think about test cases to ensure the same behavior as real browsers.