25500 2014-04-29 14:03:43 +0000 Don't escape U+0080 to U+009F in identifiers (and strings) 2014-04-30 09:44:56 +0000 1 1 1 Unclassified CSS CSSOM unspecified PC Linux RESOLVED FIXED P2 normal --- 1 jl zcorpan mathias public-css-bugzilla oldest_to_newest 104683 0 jl 2014-04-29 14:03:43 +0000 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. 104779 1 zcorpan 2014-04-30 05:24:37 +0000 http://dev.w3.org/csswg/css-syntax/#non-ascii-code-point matches the errata. https://dvcs.w3.org/hg/csswg/rev/37fa8d51b890 104784 2 jl 2014-04-30 07:02:06 +0000 U+007F, which was not covered by the errata, went from being escaped as code point to being escaped. Intentional? 104786 3 zcorpan 2014-04-30 07:45:38 +0000 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 104787 4 zcorpan 2014-04-30 07:47:52 +0000 (In reply to Simon Pieters from comment #3) > You mean, went to being not escaped? ...nevermind. :-) 104799 5 mathias 2014-04-30 09:44:56 +0000 Polyfill + tests updated: https://github.com/mathiasbynens/CSS.escape/commit/8e44737c50e0fb14a28d2c7180237935ed3787a2