254879 - Odd DIV rendering

Status: RESOLVED INVALID

(Core :: Layout, defect)

Description

[John A. Bilicki III]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3
Build Identifier: Mozilla/5.0 (Winblows; U; Winblows NT 5.1; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3

     At first glance comparing to IE 6 and Opera 7.52 it looks like Firefox is
unable to correctly render the bottom body margin.  I tested this and nope, it's
not.  I'm having difficulties trying to get all three base browsers treat my DIV
in the same manner.   'overflow: auto;' and  'position: relative;' are the least
uncooperative crossbrowser wise to get the DIV to scroll without having the body
of the page scroll (loosing the menus).
     The issue first arises from my goal of a vertically scrolling DIV.  The
issue is that a hieght or width have to be defined if the DIV's posistion is set
to absolute.  The opposite seems true for relative.  Thanks to the
so-last-century web standards from Mircrocrap I've spent all night trying to get
a 10px 10px 10px 10px margin around my DIV without resorting to using the BODY
margins as this presents issues trying to keep all my CSS on a single file for
future theme reimplemplementation.  I tried a table with padding avail.
     So far this is as close as I can get all the browsers to render the most
alike without being utterly out of whack.  I simply just want to have Firefox
render the bottom margin correctly between the body's end and the DIV border
without shooting at the flock of birds (IE and Opera) and setting me off in to
yet another aimless adventure.

Resources...

1.) CSS
     http://www.jabcreations.com/themes/ ~ You can right click and save
css-theme-classic.css which is my current CSS file.  The big class players are
BODY, DIV-CONTENT.

2.) http://www.jabcreations.com/home/nm/ ~ The N.o M.usic version of my site, I
have been using the news Area of the Home Section as reference through all this.

Reproducible: Always
Steps to Reproduce:
1. Be ambitious and creative...
2. Be willing to make a website crossbrowser compatable.
3. Breathe deeply when feelings of frustration take root.

Comment 1

[Boris Zbarsky [:bzbarsky]]

So what exactly is the problem?  Please clearly describe the difference between
expected and actual results (attach screenshots to this bug if needed).

Comment 2

[Gérard Talbot]

I think it would be a good idea to first validate your 238 css rules, 2730 lines
long CSS file and then read these 2 files:

Writing efficient CSS; Guidelines for Efficient CSS
http://www.mozilla.org/xpfe/goodcss.html

Writing perfect style sheets that are easy to maintain, quick to download,
efficient, optimized
http://www.richinstyle.com/masterclass/perfection.html

There is such a thing as CSS soup and overuse or misuse of abs. pos. elements.

As written, the description of this bugfile is not useful; a *reduced* testpage
trying to demonstrate what you believe is a bug or a spec violation in a browser
would be useful here.

Comment 3

[Anne (:annevk)]

Lack of response and an unclear bug report.

->INVALID