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

Shouldn’t BOM be handled in the byte stream prescan part? #4413

Closed
MatTheCat opened this issue Mar 5, 2019 · 3 comments
Closed

Shouldn’t BOM be handled in the byte stream prescan part? #4413

MatTheCat opened this issue Mar 5, 2019 · 3 comments

Comments

@MatTheCat
Copy link

In https://html.spec.whatwg.org/multipage/parsing.html#the-input-byte-stream one can read

A leading Byte Order Mark (BOM) causes the character encoding argument to be ignored and will itself be skipped.

The prescan a byte stream to determine its encoding algorithm doesn’t mention anything about it. Is it normal? If yes what am I missing?
@annevk
Copy link
Member

annevk commented Mar 6, 2019

This is a duplicate of #1077. The layering with the Encoding Standard which does BOM handling is somewhat broken and needs fixing.

@annevk annevk closed this as completed Mar 6, 2019
@MatTheCat
Copy link
Author

Oops sorry didn't find any issue by searching “BOM” 😅

@annevk
Copy link
Member

annevk commented Mar 6, 2019

No worries, appreciate the review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@annevk @MatTheCat