Re: [css3-syntax] CSS escape sequences from Mathias Bynens on 2012-01-12 (www-style@w3.org from January 2012)

From: Mathias Bynens <mathias@qiwi.be>
Date: Thu, 12 Jan 2012 16:42:41 +0100
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: Simon Sapin <simon.sapin@kozea.fr>, www-style@w3.org
Message-ID: <CACrCd9NJO1+qcFF6w1+n_HEXj1PLoWQzh9ioMZcjru64n3RoDw@mail.gmail.com>

On Thu, Jan 12, 2012 at 3:14 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
> I do have a question about implementations.  Gecko treats escapes as Unicode
> characters (so in particular escapes in the surrogate ranges are treated as
> invalid and replaced by U+FFFD).  It sounds like WebKit treats them as
> Unicode codepoints, period (no support for direct escapes outside the BMP).

That is correct. See https://bugs.webkit.org/show_bug.cgi?id=76152.

>  What do Presto and Trident actually do?  Do they allow both codepoint
> escapes and character escapes?  Or do they do what WebKit does?

Presto and Trident allow both. http://jsfiddle.net/mathias/jY7ra/

Only Gecko and WebKit are exceptions here, in that Gecko is the only
browser to not support the (currently) invalid syntax, and WebKit is
the only one not to support the correct syntax for characters outside
the BMP.

Received on Thursday, 12 January 2012 16:14:56 UTC