Child Selectors Being Eaten

[facetofcathy]

Just an FYI to all attempting to build skins that child selectors (>) are being converted to &gt; by the parser. One would presume the < symbol is affected too.

It does this silently, so watch out, if you've tried to use one, it's not going to work.

Submitted to support just a few hours ago, so no idea on a timeframe for a fix.

Also, if you're interested in the ramblings of a near newb tackling the archive skin the hard way, feel free to read.

Also, also, if you think having the code for Archive 2.0 all in one document would be handy, I published my Google Docs version for anyone to use. I find it really handy to Ctrl + F to find out where various code is and what it does, even though I'm not using the default skin at all.

Comments

[samjohnsson]

Yeah, the Sanitizer does eat both standalone angle brackets. Hopefully it's an easy fix, but I have no idea about the code behind the Sanitizer that does that.

Sam-the-user.

[facetofcathy]

Your reply about taming the parser had me imagining whips and chairs and other bad movie cliches.

I hope that's the only bit of weirdness, but that's a tough one to be without when you're doing global formatting from scratch.

[samjohnsson]

I have opinions regarding the Parser. About a third of them are work safe. Anyway, the Coder refereeing it did just put in a large number of fixes to it, but we hadn't seen any comment on it before, so it was something of a surprise.

sam-the-user