We don't have any tags that generate t blockquote . ']' generates t dfn .
I got stupid. The money was too good.
Jayne ,'Objects In Space'
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.
§ ita § - Jun 28, 2012 5:07:57 am PDT #3187 of 4673
Well not canonically, no, but this is transformative fiction.
-t - Jun 28, 2012 5:57:36 am PDT #3188 of 4673
I am a woman of various inclinations and only some of the time are they to burn everything down in frustration
Thanks!
SailAweigh - Jun 28, 2012 7:18:25 am PDT #3189 of 4673
Nana korobi, ya oki. (Fall down seven times, stand up eight.) ~Yuzuru Hanyu/Japanese proverb
I use cite in my CSS, so I can change the color of the text. It makes it easy to pick out what's being cited as separate from the rest of the text.
amych - Jun 28, 2012 9:05:47 am PDT #3190 of 4673
Now let us crush something soft and watch it fountain blood. That is a girlish thing to want to do, yes?
Hmm, why are we using t dfn anyway? Leaving the semantics aside, it's an inline element that we're using as block.
edit: "semantics aside". Hahahahahahahaha. I see what I did there.
§ ita § - Jun 28, 2012 10:26:12 am PDT #3191 of 4673
Well not canonically, no, but this is transformative fiction.
I can say--I have no freaking idea why I chose to bend something existing as opposed to just creating a freaking class just like how we're handling the spoiler formatting.
I would however, agree to give 10¢s; per historical usage of the ] quickedit tag to the charity of your choice. 50¢s;, even.
Sheeit, I don't even know how most browsers currently handle t dfn . Let me go look...no, nothing. AFAICT there's nothing inherent in its definition that makes it a shortcut. And the style sheet does officially force it to block. Just like I forced t cite . It's not like I didn't know...
And the only default difference between the two quickedit prompts' implementation is that the quote is displayed in monospace, and indent doesn't change the font.
My god, was I programming high?
Okay, I'm going to make the relevant changes in the code and in the main CSS file. It will affect 15 people other than me, based on a quick grep. I'll announce now and change this evening.
Jessica - Jun 28, 2012 5:11:35 pm PDT #3192 of 4673
And then Ortus came and said "It's Ortin' time" and they all Orted off into the sunset
So I'm not seeing quotes as quoted anymore. I've added the default styling that ita posted in Natter to my custom CSS sheet, and it still doesn't seem to be working.
(I logged out and the quotes were still in regular type there too, so I doubt it's my custom css that's the problem.)
I'm using Chrome on OSX, if that helps.
Jesse - Jun 28, 2012 5:13:35 pm PDT #3193 of 4673
Sometimes I trip on how happy we could be.
Ditto in IE for Windows.
Jesse - Jun 28, 2012 5:14:11 pm PDT #3194 of 4673
Sometimes I trip on how happy we could be.
And it's back!
§ ita § - Jun 28, 2012 5:18:00 pm PDT #3195 of 4673
Well not canonically, no, but this is transformative fiction.
There's no need to add default styling to your individual CSS. It's already in buffista.css.
However, I've viewed it logged in and out in six browsers on two OSes, and I can't duplicate the issue, so if someone who knows how to use the debugger on their browser would pipe up, that'd be great. Then I can see what your browser is applying.
% testing testing...
Liese S. - Jun 28, 2012 6:28:05 pm PDT #3196 of 4673
"Faded like the lilac, he thought."
It looks to be rendering correctly to me, in Firefox 13.0.1 on Windows 7. You have blockquote set to be spoilerfonting at the moment for debug?
<p>
<blockquote> testing testing...</blockquote>
</p></div>
</div>
That's how the source looks, on the page, it is grey, which is my spoilerfont setting?
eta: Okay, no it's not the exact same setting as my spoilerfont, it is separately designated in my user css.