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.

Sign up for GitHub

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

Jump to bottom

Extraneous UTF-8 BOM markers are still visible after partials are loaded from disk. #124

Closed
swijnands opened this issue Aug 9, 2013 · 0 comments
Closed

Extraneous UTF-8 BOM markers are still visible after partials are loaded from disk. #124

swijnands opened this issue Aug 9, 2013 · 0 comments
Labels
Feature request fixed / done

Comments

@swijnands
Copy link
Contributor

Partials that are loaded via the read() function will still contain the UTF-8 BOM (0xFEFF) marker (when present in the source file).

This can cause layout problems, in some browsers (at least in Chrome), because the BOM marker is regarded as a non breaking space. And thus will result in extraneous characters in your layout.

See nodejs/node-v0.x-archive#1918 for more information about this issue.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Feature request fixed / done
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@swijnands @BridgeAR