humorist + humanist (
erinptah) wrote in
style_system2012-02-17 10:32 pm
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png)
Entry tags:
Layout help, fixed & fluid (Tabula Rasa)
I'm working on two Tabula Rasa layouts -- one fixed, one fluid, with matching graphics -- and starting to hit the limit of what my understanding of CSS can handle. Help?
Here's the current state of the fixed-width layout, currently enabled at
punditfic:
And here's the fluid version, visible in action at
andthatstheword:
Issues in the fixed-width layout:
When the page isn't tall enough, module-content and module-powered show up in the middle of the sidebar. Avoided!
In the main entry view, how can I get usernames to display reliably under the userpic? The best I got (through messing with margins) was "it'll appear there, but entry text will overlap it." (Also a problem in the fluid version.) Solved in both!
New issue...when #primary is shorter than #secondary, the page only scrolls down as far as #primary.
Things in the fluid layout that I can't get to match the fixed-width layout:
On the calendar-by-month view, the entry information isn't indented with respect to the date. Prettied up!
Similarly, the bulleted list on the tags page isn't indented. Solved!
Information in the entries on the main page is all squished together (title overlapping with date/time, tags overlapping with entry tools). Solved!
Everything to do with comment display just isn't happening. The tools won't display inline, there's no space around comment-content, the header has no background... Solved!
Other issues with the fluid layout:
Can I make the #primary and #secondary divs extend to the bottom of the page (to extend the background) without covering the header?
Looks like I need to do something with module-content and module-powered here too. When the sidebar is on the left, they try to squeeze into the gap between #secondary and #primary. This isn't a problem when the sidebar is on the right (or at least, it hasn't been at my resolution). Solved!
Anyone who can point me in the right direction on any of these points would be greatly appreciated!
Here's the current state of the fixed-width layout, currently enabled at
![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png)
And here's the fluid version, visible in action at
![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png)
Issues in the fixed-width layout:
Things in the fluid layout that I can't get to match the fixed-width layout:
Other issues with the fluid layout:
Anyone who can point me in the right direction on any of these points would be greatly appreciated!
Question about:
Do you mean on this page? I can't puzzle out code until I know what page I'm on, no pun intended. :)
Also, I'll be away from the computer until possibly tomorrow, but I'll swing around again to see how things are coming along...
Re: Question about:
All your help is appreciated, no matter how fast it comes ^_^
Re: Question about:
What I normally do with that page on my own layouts is display the link to the numerical date in a really big font, make the title link proportionately smaller but not left-indented, and...not much else, really, since the whole page uses nothing but h3.titles and definition lists, which makes it a real PITA to pretty up all that much.
Example of what I do with it here: http://marahmarie.dreamwidth.org/2012/01/
If I were you, I might also want to get the word "Tags" inline with each set of tags themselves...so tell me what you want and I will try to produce the code that makes it work. :)
Re: Question about:
I want the page to look basically like the fixed version does. Time, title, username, and tags appearing as if they've been blockquoted with respect to the links to numerical dates.
And yes, I'd like to bring the word "Tags" inline! Poked at the code a bit, but couldn't guess how to make it work. Hopefully you'll have more luck ^_^;
Re: Question about:
So let's fix what I broke. Change this:
.entry-poster{float:right;clear:right;margin-left:.7em;margin-right:.3em;margin-bottom:.3em;}
To:
.entry .entry-poster{float:right;clear:right;margin-left:.7em;margin-right:.3em;margin-bottom:.3em;}
And this:
.tag ul {display: inline-block;margin-bottom:1em;}
To:
.entry .tag ul {display: inline-block;margin-bottom:1em;}
To get the page looking more like your fixed-width layout does:
.month .tag ul {/* you might not need this line since I wrote it before changing the code snippets above; try skipping it */
display: inline;}
.month dd{display:block;margin-left:30px;}
.month dl .tag {max-width:420px!important;text-align:justify;}
Also, to keep your style sheet smaller so it will load quicker, you can delete my comments (the stuff written
/* like this */
in CSS snippets) if you like.Oh and edit do you get DW notif emails of new replies like I do, and if so, did you notice what the email formatting is doing to my code? It spaces it out so that the word "margin" is like "ma rgin"....strange. Are you seeing that, too?
Re: Question about:
And we have pretty indenting. Excellent.
I'm keeping most of the comments in, for the sake of anyone (self included) who wants to use or modify the code later.
In my notification email, the random space was in "justify". I just deleted it when copying the code and proceeded as usual ^_^
So it's DW, not our email programs, it seems...
.entry-poster{float:right;clear:right;ma rgin-left:.7em;margin-right:.3em;margin-b ottom:.3em;}
To: .entry .entry-poster{float:right;clear:right;ma rgin-left:.7em;margin-right:.3em;margin-b ottom:.3em;}
[...]
.month dl .tag {max-width:420px!important;text-align:ju stify;}
It's awesome that it's flaking out for both of us on the word "justify", since that means I can screencap the relevant notif emails and submit them to Support to look at as a possible bug. I love bug-hunting, even when they sort of randomly fall in my lap like this one did. Unfortunately, I won't have time to do a Support request until tonight or tomorrow, but thanks for letting me know you're seeing it, too.
So, are both your layouts basically sorted out now? I'm not sure if you have any other questions, but if you do let me know.
New issue...when #primary is shorter than #secondary, the page only scrolls down as far as #primary
Change this:
#canvas {
overflow: hidden;
}
To:
#canvas {
overflow-x: hidden;
}
Don't thank me, because I know almost nothing about column flow, as I told
But, um, edit, while that seems to restore full navigation/scroll capability to the page, in Web Dev it's giving me a second scroll bar, and I can't even figure out what that scrollbar is attaching to at this point. I'll be offline until late tonight or sometime tomorrow afternoon but if it's also giving you double scrollbars, I'll look again to see what else you might try (setting a min-height like this:
html body {min-height: 105em;}
also works, but maybe that's not a good idea, either).Re: New issue...when #primary is shorter than #secondary, the page only scrolls down as far as #prim
I've gone back to not hiding the overflow, so at least it's usable, horizontal scrollbar notwithstanding.
Re: New issue...when #primary is shorter than #secondary, the page only scrolls down as far as #prim
until I reduce res to 800 x 600, and even then, your layout displays just a tiny bit offscreen (maybe an inch on the right) which is entirely normal for a fixed-width layout (view my own to see;(see update/edit below).Edit/update: I'm not seeing a scrollbar at 800 x 600 either, as it turns out; Web Dev gives me a scrollbar at that res, but not once I close it and view your journal normally - then there's no scrollbar at all.
Here's your fixed width layout while I'm viewing a single post on it at 1440 x 900 res: http://i.imgur.com/PuKLZ.png (and yes, when you expand the imgur image to full size on a 1440 x 900 screen, your browser might give you a scrollbar to view it with, but my browser does not give me one when I view the actual page live at that res - I have no idea why imgur is doing that).
Setting a mi-width on a main body element of no more than 730-740px will probably kill any horizontal scrollbars (and 730-740px because, despite there being an 800 x 600 res in use, actual viewport space is never more than 740px, if I recall the Internet discussions on this that I've read correctly), but it may re-introduce the other problems you've had with setting min-widths, so I'm not sure where you want to go with that at this point.
Also, you still have as an unanswered request for making the sidebar and main body match in height - but the sidebar only cuts off for me now on your Archive by month view - not on Archive by year, not on Tags, not on Main, and not on your posts.
So I'll need to look at your code more to see what's still going wrong, and I'll need you to tell me what res you're getting a scrollbar on, so I can come up with the best answer here.
Re: New issue...when #primary is shorter than #secondary, the page only scrolls down as far as #prim
With overflow:hidden turned on, the bottom of #secondary gets cut off for me on every page where #primary is too short. That includes the archive page for the year 2012, although not for 2011. It also includes the archive page for any not-too-active month.
With overflow:hidden deleted (which is how it is now), there is somehow extra space on the right. At any resolution, there's an extra 140px into which the DW navigation strip does not extend, and which compels there to be a horizontal scrollbar.
The question about making #primary and #secondary match in height is about the fluid version of the layout -- trying to get it to match more closely the look of the fixed version, where the background itself extends to the bottom of the page so the divs don't have to.
Re: New issue...when #primary is shorter than #secondary, the page only scrolls down as far as #prim
#canvas{overflow:hidden;}
back in and look again, but I'm also out of time so I probably won't have an answer until maybe tomorrow night or later (someone called in sick so I actually have to be back to work soon, and I probably won't get online again until much later).Re: New issue...when #primary is shorter than #secondary, the page only scrolls down as far as #prim
Re: New issue...when #primary is shorter than #secondary, the page only scrolls down as far as #prim
Setting a value in max-width seems to kill the horizontal scrollbar as long as the width of the window is less than that value + 140px. Any less than that, and it starts reappearing. (My screen resolution is much wider than that, but I don't keep my browser windows at fullscreen. About 1000px wide is the size that feels natural to me, and the layout reflects that.)