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:58:19 +0100
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: www-style@w3.org
Message-ID: <CACrCd9Msob_fSVeCtu=B8NyOm10Mximg1BheNiimR5JyiNCCdQ@mail.gmail.com>

> If you're proposing paving cowpaths... is this what UAs actually do?

Except for Gecko, yes.

> How do they handle unpaired surrogates?  Surrogates in the wrong order?

Let’s find out: http://jsfiddle.net/mathias/wvPdr/

In Gecko, Presto, Trident and WebKit, unpaired surrogates like
`\ud83d\uffff ` are displayed as `ud83fduffff`, i.e. the backslash
just makes the `u` character literal.

Gecko, Opera and IE treat a surrogate pair in the wrong order as
invalid and replace it with two U+FFFD characters. This seems like the
most sensible thing to do.
Only WebKit differs here: it discards the entire `content` declaration.

Received on Thursday, 12 January 2012 15:59:19 UTC