looks awful. I certainly understand that this is just a demonstration that you can put more information. But nevertheless want to look at this beautiful xf what now seems. I would like to look nicer by default (for those who want to use standard style - xenforo.)
I already said this elsewhere, but I was completely surprised this week by some members' requests to have things removed from the postbit - including medals and post count. (Not my board, just one I help out at.) They didn't like the clutter.
The way I see it (and believe me) in the beginning I didn't like the minimalistic postbit look. Then after a few days I could see the reasoning behind it that data like post count, location etc etc is just redundant bloat. It's all placed inside the membercard separate from the postbit.
To touch upon what you said in your first post. "it doesn't look nice?" is this a good enough argument to warrant putting redundant data and cluttering up a postbit? For me it's not. You weed out the bloat and this alone (think long term) gives you the option of re-inventing the postbit area by adding other features that have not even been thought of by other products.
The minimalistic look opens many doors to (i'll say again) to re-invent the postbit area. It may not seem like it now because many people are in this mindset of settling for what other products and thinking that the standard is what you are delt with. It's not. That is yet to come imo and xenforo postbit area has many options to implement with adding to exisiting clutter but inserting features that may come in the future. If that made any sense.
Whats the point of replicating what already exists? Why is it people are trying to turn XF into VB and VB into XF? Seriously... people need to just let go and either make the change or stick with what they use. But it must stop that people want to change products, but then have that product replicate exactly what they had before.
To be honest this is a little over my head too, but here's what I think is the problem: with tables you can set a height, in CSS-based design you have no tables so you can't specify the height. That height is based on the variable content in a block-level element. So the signature/links will be placed below the content in a post, the content in that post will push the signature below it....
So when the left user info block has a height that is more than the content in the post, the signature will float to the top of the post instead of to the bottom (end of the user info block). Since you don't know where that end is (it's variable) you don't know the exact placement for the signature/links.
This is a typical CSS problem and I'm afraid there's not much that can be done about it until some genius finds a way....
Devs/designers/coders please correct me if I'm wrong.
Setting a min-height is not a problem indeed. Of course the problem is to know the exact height here... Let's say you increase the min-height to 300px or whatever is needed. That may work ok in the current kitchen sink style, but when the left user info box has a lesser height the signature/links will be too low. So although you can set the min-height, there is no way to know the exact height of left/right content.
Your trick works when making a custom style indeed. When the admin knows the length of the left user info he can set a min-height for .messageContent.
But if the devs would set a minimum height with the default style, based on the longest possible user-info block, the signature/links would be too far below the content and user-info block. So that's what I tried to explain, the devs can't set a one-fits-all CSS.