Would it be bad form to search the table containing personal CSSes to see if it's even an issue?

I can't see any issue with a search to see how many people are touching it; just a few people would have a different impact than lots. (I'd also be really curious to know something about how many people are customizing at all, and how much - in a totally anonymous way, of course)

We don't have any tags that generate t blockquote . ']' generates t dfn .

Thanks!

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.

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.

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.

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.

Ditto in IE for Windows.

And it's back!

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...