Can we get a CSS fix for this?
-
http://i.imgur.com/a9z80oA.png
Apparently there wasn't enough whitespace on this forum anyway, so they shifted the category down to give you twice as much.
-
I may give it a look when I get home or get in to work tomorrow morning and see what I can come up with, unless anyone else throws something out first.
-
i'll second the request, that's silly that it does that.
-
Someone should ask @codinghorror why that was done. I think the explanation is likely to be teeth-grindingly annoying.
-
You can feed poor people with whitespace. This software is working wonders.
-
Not to Jeff it isn't. It's civilised that way. Real topics don't get that long and therefore don't have that many posters in.
-
Someone should ask @codinghorror why that was done.
My bet is at "reduces visual clutter" (aka. the reason why there were almost enough rules behind showing the in-reply-to indicator to warrant a decision system).
-
Long topic names? You're Doing It Wrong™.
-
@chubertdev Is Doing It Wrong™<t3688p8>
-
Not to Jeff it isn't.
I would have assumed it was obvious it would be annoying to us. Obviously he would think We're Doing It WrongTM
-
Someone should ask @codinghorror why that was done. I think the explanation is likely to be teeth-grindingly annoying.
Or simple: He wanted to piss of TDWTF.
Edit: Ah, you Hanzo'd me up there .
-
Discosearch to the rescue:
This doesn't seem crazy:
Another advantage is that it lets you have somewhat longer category names (3 words, longer words) without much consequence. And combine them in category / subcategory form too.
-
I quite like to have separation of concerns in different lines.
-
Another advantage is that it lets you have somewhat longer category names (3 words, longer words) without much consequence. And combine them in category / subcategory form too.
Oh look, they're actually concerned about edge cases instead of dismissing them as "only TDWTF would do that".
I sorta agree with the sentiment, but THERE'S SO MUCH ROOM THERE. And you can always break the title into two lines if it overflows.
And this doesn't make sense:
I find that over time I've started to really dislike our categories-in-front design. Category is very important, but putting it in front of the title might be a bit too strong.
Putting it in its own separate line is even more strong and emphasizing.
-
Yeah, it's a mystery as to what will be "too strong" to Jeff. I'd also like to emphasize that your "quotes" of me were actually me quoting Jeff.
-
I'd also like to emphasize that your "quotes" of me were actually me quoting Jeff.
Fix'd. Lack of automated nested quoting when quote-replying is a bitch, but there's probably no way we can get that without a kidnapping and blackmail in order.
-
I’ve noticed that on mobile the suggested topics list also puts categories on their own line, wasting precious space.
I don’t use the mobile interface often so maybe it was already like this, though.
-
Well, considering the layout of the elements, I don't think it'd be possible to make it so the category shows up right before the title with just CSS (or at least it's beyond my capabilities).
The best I can do, to minimize the spacing up top, is this:
[code]
#topic-title .container {
margin-top: -25px;
}
[/code]I hate their damn preview window/parser sometimes. Tried doing that with triple backticks at first and it was screwing up, so I just went with [code] blocks.
-
I don’t use the mobile interface often so maybe it was already like this
It has, to my memory, always been like that on mobile.