Escape sequences and new CSS parser?

Fri, 21 Feb 2003 22:22:45 -0800

The main CSS page on W3C (which worked in the old parser) is now hosed 
because of the escape characters used in conjunction with the content 
property.   Did I miss something in the merge, or does the flex/bison 
combo have trouble with these?

<html>
<head>
<style>
p.date:before {
   content: "\a0\a0\a0\a0\a0\a0";
}
</style>
</head>
<body>

<p class="date">Hello</p>
</body>
</html>

In the above example, I see what appear to be spaces, but then I also 
see the \.  I see one less \ than the number of "\a0" that I specify, 
and I also get a line break (oddly) at the end.

Any tips/pointers?  I see this ParseString object with an unsigned 
short* and a length field, but I'm totally at a loss as to how that 
gets filled in.

dave