This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Characters in this range were made valid (part of "non-ASCII code point") as part of this errata: http://www.w3.org/Style/css2-updates/REC-CSS2-20110607-errata.html#s.4.1.1b It's unclear why they should be escaped when serializing.
http://dev.w3.org/csswg/css-syntax/#non-ascii-code-point matches the errata. https://dvcs.w3.org/hg/csswg/rev/37fa8d51b890
U+007F, which was not covered by the errata, went from being escaped as code point to being escaped. Intentional?
You mean, went to being not escaped? No, that was bogus, DELETE still needs to be escaped. Thanks. https://dvcs.w3.org/hg/csswg/rev/2c75e9e61710
(In reply to Simon Pieters from comment #3) > You mean, went to being not escaped? ...nevermind. :-)
Polyfill + tests updated: https://github.com/mathiasbynens/CSS.escape/commit/8e44737c50e0fb14a28d2c7180237935ed3787a2