[Webkit-unassigned] [Bug 66085] The HTML parser doesn't ignore the BOM when the HTTP charset=foo conflicts with it

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Aug 12 21:44:00 PDT 2011


--- Comment #1 from Alexey Proskuryakov <ap at webkit.org>  2011-08-12 21:44:00 PST ---
A BOM is most authoritative indication of encoding, because there are few ways to get it wrong. It's much easier to get an encoding declaration or an HTTP header wrong.

There are some synthetic examples of strings in other encodings that can be mistaken for a BOM, but it hasn't been a practical issue.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list