erinptah: (winding road)
humorist + humanist ([personal profile] erinptah) wrote in [community profile] style_system2012-02-17 10:32 pm

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 [community profile] punditfic:




And here's the fluid version, visible in action at [community profile] 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!
    marahmarie: (M In M Forever) (Default)

    Always a but (or in IE's case, yeah, a butt)...

    [personal profile] marahmarie 2012-02-21 10:19 pm (UTC)(link)
    IE old doesn't get it

    Heh, why would this not surprise me? There's a reason my Quick Launch thingy includes stuff like:




    So you have to be able to put a conditional style on it

    But if by that you mean a conditional comment, yeah, I'd love to trick IE Old out in just that way with all my layouts, but DW/LJ strips out such possibilities by invalidating your entire style sheet for improper syntax if you include that code. You can't use backslashes, any non-UTF8 chars or any conditional comments. And of course, you can't link off-site to additional or even primary style sheets. Which might sound like a complaint on my part, but is actually one of the reasons I love coding for DW more than any other place (such as my own website or Wordpress, or whatever); you're so limited in what you can do here that you're forced to get really creative to make stuff work at all.

    While I would enjoy the added flexibility of Moar Options, there's something to be said for having to work within such narrow confines, too.

    And, crucially, some screen readers treat it as if it was a table, delivering the information as if it's tabular data. Which I don't think they should do.

    Thanks for mentioning that because I had no idea. Assuming all display: table values have the same effect, that's bad news indeed. I began using display: inline-table after noticing Google uses that to set some elements
    on results pages, and I found it comes in handy for coding forms....but...if it's going to hurt accessibility, then I need to find a better way, I guess.
    Edited (more info) 2012-02-21 22:35 (UTC)