Bug 33101 - Microsoft BOM (Byte Order Mark) does not spawn error in console.
Summary: Microsoft BOM (Byte Order Mark) does not spawn error in console.
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: CSS (show other bugs)
Version: 525.x (Safari 3.2)
Hardware: PC OS X 10.5
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-01 22:57 PST by John A. Bilicki III
Modified: 2011-08-12 21:39 PDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description John A. Bilicki III 2010-01-01 22:57:24 PST 
My WebKit CSS3 files (per Safari version) each contained a byte order mark that got past me. No errors were reported in the console however Safari was not rendering things from the style sheet.

While partly my fault it would be very helpful to have WebKit based browsers report an error in the console when encountering the byte order mark.

I edit using a freeware program called SuperEdi that has the ability to enable/disable the BOM and would be useful for verifying any fixes.

I'm currently using Safari 4.0.4 on 32 bit XP.
Comment 1 Alexey Proskuryakov 2010-01-02 11:44:40 PST 
Could you please provide a test case? Safari supports byte order marks in CSS files as required by CSS specification, see paragraph 4.4 at <http://www.w3.org/TR/CSS2/syndata.html#syntax>. So, a BOM shouldn't make parsing fail.
Comment 2 Alexey Proskuryakov 2011-08-12 21:39:50 PDT 
No response, closing.