Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

Apparently, if tags wrap to a second line in a question listing, the "recent activity by" div gets pushed down an extra line.

Unusually wide gap if tags wrap to next line in question listing

share|improve this question
I haven't heard that phrase since I had braces. – mmyers Mar 16 '10 at 22:15
Uuh... and and the problem with this is... what? Something that spanned two lines took up, oh gosh, two lines! – Mark Henderson Mar 16 '10 at 23:12
@Farseeker, it's unnecessarily attention-grabbing. – devuxer Mar 16 '10 at 23:33
I doubt it was done on purpose... – Mark Henderson Mar 17 '10 at 0:33
@Farseeker, I'm not saying the user did it on purpose, I'm just saying there is no reason his question should stick out from all the others. – devuxer Mar 17 '10 at 0:46

I'd say somebody needs to use shorter tags. I mean, webdeploymentproject? badimageformatexception?

share|improve this answer
BadImageFormatException is a built-in .net type, so it's OK (if exception names are generally ok as tags) -… – Michael Stum Mar 16 '10 at 22:32
But if you use really long tag names, you get rewarded by having the widest, most attention-grabbing question on the page. – devuxer Mar 16 '10 at 22:36
@Michael didn't know that, that makes it okay. Still, the other ones don't make sense. @DanM true! – Pëkka Mar 16 '10 at 22:41

Regardless of the length of the tags, I don't think the question is any more rewarded for being the most attention-grabbing question on the page. If someone were interested in those tags, they're gonna read the question. And, too, if the question is poorly written, then the alleged reward won't be so great.

I don't see a problem with the extra gap, either.

I do agree, however, that the tags are extremely long. Why not shorten the tags when not describing a specific built-in type (as @Michael Stum points out)? For instance:

  1. webapplicationproject -> webappl-proj
  2. webdeploymentproject -> webdeploy-proj

These are just off the top of my head, but I think they are a reasonable place to start.

Even still, BadImageFormatException can be shortened to an accepted abbreviation: BadImageFormatExc.

share|improve this answer
I'm definitely not defending the tags used in that example, I was just browsing the question listing and thought this question stuck out from all the others by being way wider. But I guess I'm the only one who thinks this is a problem. – devuxer Mar 16 '10 at 23:36

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .