Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UTF-8 byte order mark (BOM) not stripped #150

Open
westonruter opened this issue Nov 20, 2018 · 1 comment
Open

UTF-8 byte order mark (BOM) not stripped #150

westonruter opened this issue Nov 20, 2018 · 1 comment

Comments

@westonruter
Copy link
Contributor

I was debugging an issue with @font-face not being recognized as an at-rule. It turned out to be because there was a UTF-8 BOM (\uFEFF) at the beginning of the CSS file and this was tripping up the parser. I assume this should be stripped when parsing, correct? Would this be part of improved @charset handling?

@sabberworm
Copy link
Contributor

Yes, BOM handling was part of the work on #116 and when we revisit that, we’ll surely handle the BOM gracefully. I think in general the BOM contains useful hints about the charset of the file in question (especially if @charset is missing or conflicting).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants