Oh hey, that did it for me. Stupid cache!
I don't fancy spending the next month trying to get librarian out of the carpet.
Spike ,'Chosen'
Buffistas Building a Better Board ++
Do you have problems, concerns, or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.
Jesse - Jun 29, 2012 8:48:37 am PDT #3219 of 4673
Sometimes I trip on how happy we could be.
§ ita § - Jun 29, 2012 9:00:06 am PDT #3220 of 4673
Well not canonically, no, but this is transformative fiction.
God damn it! I swear we put in code to try and force that refresh, but I guess it never worked.
Okay, I'll note that in Press.
Jessica - Jun 29, 2012 11:55:01 am PDT #3221 of 4673
And then Ortus came and said "It's Ortin' time" and they all Orted off into the sunset
You have a space in front of the % sign,
Oh, oops. That'd do it.
% percent
carat
Jessica - Jun 29, 2012 11:55:22 am PDT #3222 of 4673
And then Ortus came and said "It's Ortin' time" and they all Orted off into the sunset
Now they're both indented and monospace.
§ ita § - Jun 29, 2012 1:26:19 pm PDT #3223 of 4673
Well not canonically, no, but this is transformative fiction.
I feel both heartened and chastened simultaneously.
Typo Boy - Jun 29, 2012 2:33:03 pm PDT #3224 of 4673
Calli: My people have a saying. A man who trusts can never be betrayed, only mistaken.Avon: Life expectancy among your people must be extremely short.
In terms of why it did in my browers I(and I know this is belated) because this is how I told my browser (unintentionally) to handle monspaced. You can have all the css you want, but the browser still decides how to handle the css commands. And if you tell then to, browsers will overide just about anything.
In one broswer it was handling multiline monospace as monospace,but single line monspace as normal text. And the broswer decided that block quote was multi-line even if it only had a line of text, but that cite was (percent) was single line and thus handled as non-monospaced - regardless of what the css said. Something else along those lines was happending in the other browser involving serif and non-serif fonts. I won't bore you with that onem, because the key is that browser settings can override anything in terms of appearance and past a certain point, it is not the developer's problem.
Liese S. - Jun 29, 2012 5:10:25 pm PDT #3225 of 4673
"Faded like the lilac, he thought."
Is <cite> still getting stripped?
§ ita § - Jun 29, 2012 6:00:36 pm PDT #3226 of 4673
Well not canonically, no, but this is transformative fiction.
Yes. Do you need it? It seems to be unpredictable in many browsers, varying between nothing and italic.
Liese S. - Jun 29, 2012 6:34:22 pm PDT #3227 of 4673
"Faded like the lilac, he thought."
No, I don't need it. But the tag itself is problematic where the quickedit wasn't? That's curious.
§ ita § - Jun 29, 2012 6:49:29 pm PDT #3228 of 4673
Well not canonically, no, but this is transformative fiction.
The quickedit was wrong, though.
There's a pretty short list of allowed tags. it's easier to manage that way. You need t small t big t code or t pre --you're all hooked up. But most of the semantic tags are out.