25426 2014-04-23 09:23:16 +0000 Don't escape --foo 2015-09-08 07:03:47 +0000 1 1 1 Unclassified CSS CSSOM unspecified PC All RESOLVED FIXED P2 normal --- 1 zcorpan zcorpan mathias public-css-bugzilla oldest_to_newest 104253 0 zcorpan 2014-04-23 09:23:16 +0000 http://dev.w3.org/csswg/cssom/#common-serializing-idioms [[ If the character is the second character and is "-" (U+002D) and the first character is "-" as well, then the escaped character. ]] css-syntax changed to allow --foo so maybe CSS.escape() shouldn't escape it? 104781 1 zcorpan 2014-04-30 05:27:27 +0000 https://dvcs.w3.org/hg/csswg/rev/98c61628c0e9 104798 2 mathias 2014-04-30 09:44:36 +0000 Polyfill + tests updated: https://github.com/mathiasbynens/CSS.escape/commit/3ff1913c7ac411a9108ef528aceb3cb6c1e0918d 123123 3 mathias 2015-09-07 18:08:10 +0000 This is problematic in browsers that ship `CSS.escape` before shipping an updated CSS parser (as per the latest css-syntax): https://code.google.com/p/chromium/issues/detail?id=528972#c3 123124 4 zcorpan 2015-09-08 04:35:49 +0000 - and -- are not identifiers. Blink implements css-syntax. This is a bug in CSSOM. https://drafts.csswg.org/css-syntax/#ident-token-diagram 123126 5 zcorpan 2015-09-08 06:49:34 +0000 https://github.com/w3c/csswg-drafts/commit/196e80a5013df9f185547df3fdeccc72f9aae597 123127 6 zcorpan 2015-09-08 07:03:47 +0000 Oops, misread css-syntax. '--' was OK. https://github.com/w3c/csswg-drafts/commit/7707b15e6d42a6cb4b04da6b6ecb680c0e9365da