[Bug 4828] Unicode BOM at beginning of file not stripped, causes parse errors from bugzilla@wiggum.w3.org on 2007-06-28 (www-validator-cvs@w3.org from June 2007)

From: <bugzilla@wiggum.w3.org>
Date: Thu, 28 Jun 2007 00:57:35 +0000
To: www-validator-cvs@w3.org
CC:
Message-Id: <E1I3iKF-0002lv-LF@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=4828


ot@w3.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                URL|                            |http://jigsaw.w3.org/css-
                   |                            |validator/autotest/testsuite
                   |                            |/bugs/4828-bom_atmedia.css
           Severity|normal                      |major
           Platform|Macintosh                   |All




------- Comment #1 from ot@w3.org  2007-06-28 00:57 -------
examples:
http://jigsaw.w3.org/css-validator/autotest/testsuite/bugs/4828-bom_atmedia.css
has a BOM at the beginning, starts with @media
=> parse error Parse Error - &#65533;&#65533;&#65533;@media screen

http://jigsaw.w3.org/css-validator/autotest/testsuite/bugs/4828-bom_notatmedia.css
has a BOM, starts with body selector
=> source display has garbage characters

Received on Thursday, 28 June 2007 00:57:53 UTC