Your signature is an eyesore.

Probably the latter, because it looks fine in that post.

That's probably it then, because he was making it really fething small. Someone should block him for unfunny vandalism.

I agree, somebody should. Also, it looks totally stupid in LQT.

It looks broken in LQT. Or is the [[User:Inquisitor Ehrenstein| part supposed to be visible?

No, the ector]] has been chopped off the end, ruining the link. He's lucky that it doesn't look even worse, really.

@Peter, that makes sense. Is there a tighter character limit on signatures in LQT than in normal preferences?

That would appear to be the case, though I don't know for sure.

My guess is that for whatever reason LQT doesn't like the <span> being used within a link. The same font formatting could be used without it being a span & it would probably work OK (like mine or yours does).

It's a simple character cutoff in the code. If he removes all the extra spaces in his style, and reduces the font size of the text and/or the smiley below 10, he might manage to get it to work.

Couldn't they avoid the character cutoff in the first place by setting their signature to transclude, rather than substitute, in their signature? It's what Blue and I do.

Manually removing the "subst" from the sig part below is also an option, as is not using LQT in the first place.

Copy this to your CSS page:

.sashasig {
     background: #D8D8D8; 
     padding: 2px; 
     color: #151515; 
     font-size: 12px; 
     border: 1px solid #1F1F1F;
}

If you could add a class for the eyes part of the sig too that would be most appreciated.

Here's an idea, Inquisitor: you change your CSS page to prettify your own sig, just so you can see it. Don't force others to change theirs just to accommodate your eyesore of a sig.

That's what he did.

Ah. Sorry. Inquisitor had been pretty insistent about his sig, so I figured he was continuing to be as minimally accommodating as possible.

I'm pretty sure it's a plain link the way it was before.