Height: 100%
Moderator: Thought Police
Height: 100%
Any help on the best way to implement table height so that it fills 100% of the window vertically? Got a repeating bar (background image: repeat-y etc) down one side, works in IE but not in Firebird.
Currently using:
<table ... height="100%">
Currently using:
<table ... height="100%">

-
- Thought Police
- Posts: 1205
- Joined: Thu Mar 14, 2002 12:11 pm
- Location: Macclesfield
- Contact:
-
- Thought Police
- Posts: 1205
- Joined: Thu Mar 14, 2002 12:11 pm
- Location: Macclesfield
- Contact:
It doesn't have to be in a table, just that's what I'm comfortable with. I'm going for the centred 800x600 table, but I'm trying not to fall into the 3-column, navigation on the left thing.
I do have the doctype declaration (transitional one); the html and the css validated. (Up to the point I started changing things).
I'm in the slap-it-all-in-and-worry-later stage.
I do have the doctype declaration (transitional one); the html and the css validated. (Up to the point I started changing things).
I'm in the slap-it-all-in-and-worry-later stage.

-
- Alpha (Conditioned)
- Posts: 2345
- Joined: Sat Mar 16, 2002 7:31 pm
- Location: Inside my own head
- Contact:
Yeah, we had that problem before on the school site - if the body is longer that the screen height we couldn't find a way to make the sidebar the right length. Still works for a lot of things tho. I'm still not sure he's 100% right in this case tho - for my site (mindshark.net) I've been playing around with coloured bars made with div tags, and specifying margins allows you to place them quite comfortably - and this is using divs with a defined background colour and placement but no other attributes or content
"Why do you hate America so much?"(TM)
http://lists.evolt.org/archive/Week-of- ... 39560.html>
> > It's a conundrum. The W3C doesn't even know!
>
> The CSS 2 recommendation does spell it out [1], sort of -- but with
>much wind, leaving a wake of confusion. To set one object's height to 100%
>of the height of its containing block doesn't seem so complicated. But what
>seems to be the tripping point is what to do when an element -- namely, the
>html element -- is at the top of the hierarchy and has no containing block.
>The obvious answer would appear to be that setting the height of the html
>element to 100% would be 100% of the viewport, as was essentially the
>traditional behavior of browsers (although it's probably more accurate to
>say that a 100% height on the html -- or, in the old days, the body --
>element was equivalent to min-height: 100%, since such elements would
>freely expand if their content exceeded the height of the viewport). Maybe
>a value of "viewport" should be added to height/min-height/max-height just
>to help
>settle the issue...
The connection between the HTML document and the viewport is one of the
greatest problems/unexplored areas in the standards. Basically, to whichever
standard you go you'll find problems in exactly this area
CSS - the height problem described here
DOM - W3C doesn't define any properties of the viewport, like clientWidth,
or the HTML document in connection with the viewport, like scrolling
offsets.
W3C doesn't have the faintest idea what to do with the viewport.
Kajun is awaiting approval.
Thanks for that CSS maxheight tables link. Might be worth a try, but I've seen too many issues with differences in the way they're rendered - or just the fact my brain would probably fail trying to do it. The format I've got now is a 760 width table nested inside a 100% width table - without the sidebar image I was originally after.
