[Bug 19882] @charset rule logic is not case insensitive & should state ASCII interpretation for clarity

https://www.w3.org/Bugs/Public/show_bug.cgi?id=19882

Kang-Hao (Kenny) Lu <kennyluck@csail.mit.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kennyluck@csail.mit.edu

--- Comment #9 from Kang-Hao (Kenny) Lu <kennyluck@csail.mit.edu> ---
(In reply to comment #4)
> @charset"utf-8";     yes

I was puzzled by this as the code is pretty clear. Then I figured "b1"'s data
URL isn't correct.

It now gives me:

@charset "utf-8";    yes
@CHARSET "utf-8";    no
@ChArSeT "utf-8";    no
@cHaRsEt "utf-8";    no

@charset"utf-8";     no
@charset  "utf-8";   no
@charset\9"utf-8";   no
@charset\A"utf-8";   no
@charset\C"utf-8";   no
@charset\D"utf-8";   no
@charset "utf-8" ;   no
 @charset "utf-8";   no

@charset 'utf-8';    no

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Firefox/17.0

(In reply to comment #7)
> ... and unfortunately, IE9 appears not to support this use of data: URLs, so
> I'm going to have to redo the test case with a whole bunch of tiny
> supporting files to get that to work. :-(

So I did that for you ;)

@charset "utf-8";    yes
@CHARSET "utf-8";    no
@ChArSeT "utf-8";    no
@cHaRsEt "utf-8";    no

@charset"utf-8";     no
@charset  "utf-8";   no
@charset\9"utf-8";   no
@charset\A"utf-8";   no
@charset\C"utf-8";   no
@charset\D"utf-8";   no
@charset "utf-8" ;   no
 @charset "utf-8";   no

@charset 'utf-8';    no


Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2;
.NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC
6.0; eSobiSubscriber 2.0.4.16; .NET4.0C)


It's not suprsing to me as CSS 2.1 is OK clear here:

  # @charset must be written literally, i.e., the 10 characters '@charset "'
  # (lowercase, no backslash escapes), followed by the encoding name, followed
  # by '";'.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 7 November 2012 00:06:52 UTC