*wry* It would be easier to make a working layout, yes, but IJ is still taking updates from the LJ core code, as it becomes available. And if we change the core code here, then updates will have to be hand-merged and that would be a big pain.

And anything you happen to figure out will be very welcome!

I'm making progress. Hopefully in a couple hours you'll have the fix you need (I am double checking in IE7 - do you know of any significant css differences between IE6 and 7 that I should worry about?)

You are wonderful.

The only difference I know of for sure is that the * at the front of a css rule (as in the Holly Hack) no longer works in 7. I think the underscore does, though.

Here we go! I had to remove the hr and replace with a border, but it looks spic and span (I didn't test in anything but entry mode, so let me know if there's still quirks).

http://home.comcast.net/~isentropic/css.css

Also, if I could offer my humble aesthetic opinion, I'm finding that

a {color:#584f34}
a:visited {color:#8e886b}
a:hover {color:black;}

table.IJ-AccentBox2 { background: #edebd5;}

Are a little easier to see/read/etc.

Annnnd I'm not sure if something changed since I got home from work, but comments are no longer indented. O.o

*blinks* Nothing that I know of... *checks* They're indented in Camino (which is the Geko engine just like FF). How peculiar.

But! If it really is the hr, then I'm going to try one more thing before going with the borders. Thank you for hammering this out!

And I like the colors you suggest. We'll give those a try. Probably not until tomorrow, though, since Squeaky is likely in bed by now.

Billionth comment? Billionth comment. I reuploaded the css because I did something weird with padding that I didn't realize till five seconds ago. The code fixes the gap at the bottom (that you originally needed so that big fonts could work) and the hr problem.

It /does? *sparkles* Where did you put it?

Its the comcast link up about three comments ago.

Ah, sorry, I meant, where did you put that padding? I can't spot it in any of the likely places...

Ah! I'd put it in the sidebar (reduced to 140px and added padding-right of 5px) - I removed it already so that css file is good to go :)

Okay, now I get it! I should probably go to bed now. *laughing*

I remember Safari used to be a right pain about heights in percentages; let me test it in that browser. With luck the problem has been fixed, and this will work out!

Thank you again!

Fingers crossed!

*glum* Alas, Safari is still being pissy about it. *sighs* guess we're stuck with a space at the bottom.

http://www.ibloomstudios.com/articles/safari_css_hack/

Maybe this will help? Because I know its working for firefox and IE so if we can just cut safari out of the css loop, we'd be good to go

*frustrated* No dice. Safari looks like it's fixed that loophole. It looks like all Gecko browsers on the Mac (Firefox, Camino, etc.) won't accept the percentage height in any case. They interpret it as 100% of the content in that div, not of the page as a whole.

I wish there was a way for me to look at mac browsers on a PC.

The other possibility is to use a browser-css selector.

*wry* I hear you.

Hm. Do you know if there's a way to apply them to different platforms? Because we'd need to include FF for Mac in the 'pixel height' style while putting FF for PC in the 'percentage height' style.

Alternatively, we could just put out a user-styles patch for IE and FF-PC users that uses the percentage height and at least they could have a no-gap layout.

I like patches personally, but there are a lot of people who can barely find the viewing options page, much less figure out how to use patches - unless it is something that can be easily accessed through the viewing options page. I also like browser-directed css because a lot of people use one kind of browser at home and another at work and anything set by IJ for your account won't work in both cases. Blah blah etc etc it's kind of lose-lose.

This is the best thing I've seen, though I've never used it:
http://rafael.adm.br/css_browser_selector/

I think you can either set browser specific tags or direct them to browser specific css files.

Ooooo! What a clever bit of code! I'm sure that could be added to the header javascript. I'll send it to Squeaky see if that works.