100% Vertical div overflow problem [Archive]

Click to See Complete Forum and Search --> : 100% Vertical div overflow problem

jwilliams

11-14-2006, 10:23 PM

I have, essentially the following css code:

html, body, #container { height: 100%; }

for the html:

<html>
<body>
<div id="container">

</div>
</body>
</html>

If you open the page in a very small window, then scroll down, the text overflows the div#container. Is there anyway to force the the container div to go past 100% of the window? Thanks.

Here's an example of what I'm talking about:

http://acm.cse.lehigh.edu:81/~jhw204/bin/duke/

Also, html{ height:100%; } is not valid strict 4.01. Is there any way to get that effect without an html line (while still using doctype strict ;-) )?

Kravvitz

11-15-2006, 12:13 AM

1) Height and Min-Height (http://www.dynamicsitesolutions.com/css/height-and-min-height/)

2) Huh? Where did you put that style rule?

jwilliams

11-15-2006, 12:25 AM

min-height doesn't validate, bro. i put my stylesheet in styles.css.idontknowballs. Anyone else? Thx/facepwn3d (2thaface.)

Kravvitz

11-15-2006, 12:52 AM

min-height is valid CSS2. (http://www.w3.org/TR/REC-CSS2/visudet.html#propdef-min-height)

Perhaps you are using the word "validate" incorrectly.

IE6 doesn't support min-height. IE7 does though.

jwilliams

11-15-2006, 02:16 AM

Touché, stranger of the interweb. IE7 is not the dominant browser though. Further, it doesn't support CSS2.0, still, after fooking like ten years. **** is so ****ing geylame. W/e. http://www.w3.org/TR/REC-CSS1 is the spec we live by until mo****as quit using that lame **** and pony up with some mozilla 1.5. (2.0 freezes, and the memory leak issue never got fixed.)

Every 45 days my dad calls me and tells me his computer has a virus, and I ask, "Dad... have you been using Internet Explorer still? What have we talked about. I am a young tech savy engineering student!" **** IE. <3 W3 <3. Anyway, let's solve some W3 CSS problems V1 style. Don't use IE, don't use CSS2.0 cause some people use IE, and for the love of god, when XHTML2 becomes a recommendation, don't even give the spec page a hit for that filthy W3 stat engine. I'll turn off all my servers before we have no <a> element. Idealism is not the semantic web, unfortunately. But, we'll imagine a Firefox 1.5 without a memory leak and a functional search bar, and call that our spec. It's (basically) XHTML1 application/xhtml +CSS2. goodtimez!

Anyway, lets quit waving "I've read the W3 spec sheets" ****s and solve this problem. Sorry about the rantz thx slutz.

Kravvitz

11-15-2006, 03:58 PM

But IE6 supports a lot of CSS-P and that isn't included in CSS1 but is in CSS2.

So you refuse to use anything that IE6 doesn't support even when there is a work-around for it? Why?