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 3127 - Source output escapes backslashes where it should not
Summary: Source output escapes backslashes where it should not
Status: RESOLVED FIXED
Alias: None
Product: CSSValidator
Classification: Unclassified
Component: Other (show other bugs)
Version: CSS Validator
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Olivier Thereaux
QA Contact: qa-dev tracking
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-21 05:45 UTC by Olivier Thereaux
Modified: 2008-03-28 09:12 UTC (History)
0 users

See Also:

Attachments

Description Olivier Thereaux 2006-04-21 05:45:18 UTC 
if a line in the css source begins with a backslash, the section with the output of the Valid CSS information omits it, thus making the code shown (often) invalid.
Comment 1 Yves Lafon 2008-03-27 17:52:23 UTC 
I would need more information there.
\foo { color: red; } will be seen as unicode \f followed by oo,
while \oof will be recognized as 'oof'

See http://www.w3.org/TR/CSS21/grammar.html
Comment 2 Yves Lafon 2008-03-28 09:12:04 UTC 
Fixed by changing the convertIdent to canonicalize instead of creating unicode characters.
Here is an example that now works:
\foo {
color: green;
}
now gives 
\00000foo {
color: green;
}
(a valid output).