This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 25426 - Don't escape --foo
Summary: Don't escape --foo
Alias: None
Product: CSS
Classification: Unclassified
Component: CSSOM (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Simon Pieters
QA Contact: public-css-bugzilla
Depends on:
Reported: 2014-04-23 09:23 UTC by Simon Pieters
Modified: 2015-09-08 07:03 UTC (History)
1 user (show)

See Also:


Description Simon Pieters 2014-04-23 09:23:16 UTC

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?
Comment 1 Simon Pieters 2014-04-30 05:27:27 UTC
Comment 2 Mathias Bynens 2014-04-30 09:44:36 UTC
Polyfill + tests updated:
Comment 3 Mathias Bynens 2015-09-07 18:08:10 UTC
This is problematic in browsers that ship `CSS.escape` before shipping an updated CSS parser (as per the latest css-syntax):
Comment 4 Simon Pieters 2015-09-08 04:35:49 UTC
- and -- are not identifiers. Blink implements css-syntax. This is a bug in CSSOM.
Comment 6 Simon Pieters 2015-09-08 07:03:47 UTC
Oops, misread css-syntax. '--' was OK.