In the latest version of Discourse, the username and timestamp is closer to the top border of posts than the avatar, making them misaligned. The read marker is as before and thus also misaligned.
The bottom buttons in posts are 15 px from the bottom border. Avatar is 15 px from the top border.
I can only imagine this being unintentional, and you’re probably already aware of it. Didn’t know what to search for, so I apologise if already reported.
I am a bit confused, can you attach some before and after screenshots?
Hmm, do you know an unupdated Discourse forum? I’ll go look!
Compare with this:
This is 1.4.0.beta 7 … http://forum.tycoonmarket.com/t/shades-of-what-you-say/18541 looks just like it does here:
vs:
So not following what changed …
Huh. Here’s how it looks for me, and apparently another person I spoke with.
It looks as it should in Safari!
Disabled all my Firefox extensions to see if any of them caused it, but they do not seem to have.
I don’t know how many pixels, but with Firefox and Chrome it looks to be about a 0.5em difference between the top of the avatar and “name” and “time”.
Not all that noticeable to me, especially with round avatars, but it is there.
It looks to be the .topic-body { padding: 5px 11px 2px; } vs.
topic-avatar { padding: 15px; }
I think you are complaining about this by @rubo77 :
https://github.com/discourse/discourse/pull/3954
Which imo is just too hacky anyway… I don’t really agree with this change so going to revert it, it leads to the topic view not having a consistent view and I don’t think it is needed.
If you wanted to save the 10px .topic-avatar could be given a “top” to match.
Remember the read tracking marker and “Reply as linked topic” too if wishing to compact it. I’d probably remove the same amount of space for the buttons at the bottom of posts as well.
It should save as much height as possible on screens smaller than max-height: 700px
(sure you can simulate this on bigger screens with CTRL + to zoom)
I follow the intentions here, but don’t feel like the support weight is worth it in this case. It is easily done in a site customization.
I still don’t see the problem. Where is some space missing or too much? can you show a screenshot please?
Compacted:
Not compacted:
There’s a screenshot in an earlier post.
I just don’t see the value in a compacted view based on browser height… it just feels odd to me and a support burden. This was the only case where we changed behavior based on height, all other spots are based on width.
On small screens you are happy about every inch you save, so you can see some more posts at the same time on your screen (in a large good readeable font)
For example, I have an 11’’ screen on my laptop and I don’t want to scroll past all these white areas between every post
I would probably not prefer the compact view even with everything properly aligned.
I use an 11″ 1366x768 display, and while I can understand the desire, I believe I disagree with having it by default.
so lets take it effect a bit later, lets say smaller than 600px
this will fix the “reply as lilnked” and the time position:
.topic-meta-data .post-info {
margin-top: -2px;
}
.gutter .post-links {
margin-top: -5px;
}I just feel this is much better fitting as a site customization, you can make a topic for it here with screenshots and all. If there is strong drive from the community to include it in core we can revisit this in a few months.
As it stands it just feels a bit hacky and unfinished.
Usually users wouldn’t see it anyway if they have normal large screens, higher than 600px. On small screens Discourse is really hard to use.
And as visitor you cannot change the view of discourses, that you visit somewhere in the web. So the default installation should reach all users with small screens.
Sure, I really like it like this with those two rules added. What are other opinions?
Does it trigger in small windows on large displays?
Please implement it well and take good screenshots as @sam suggested. Present the whole thing and it may find its way in. I’m not wholly against it, and I understand you want it in all Discourses you visit without having to do something extra for each one. Not to mention the feature may well make sense with the right implementation. I’m just not sure yet. Convince us!