Closed
Bug 19249
Opened 26 years ago
Closed 26 years ago
padding in a positioned div adds undesired space to bottom of entire page
Categories
(Core :: Layout, defect, P3)
Tracking
()
VERIFIED
FIXED
M15
People
(Reporter: mikeque, Assigned: troy)
References
()
Details
See above mentioned URL in M11. Scroll to bottom of page and notice white gap
below bottom of green bar. That is not specified and is a layout bug.
Defined style .LycNet is applied black bar on page. When I remove
the "padding:" attribute, the space at bottom of page is fixed.
| Reporter | ||
Comment 1•26 years ago
|
||
Another example:
http://staff.hotwired.com/mikeque/mozilla/padding2.html
In this case, the green should not protude to the right of the red rule. If I
remove either the padding or width attribute from ."options", the green bug is
fixed, but I'm losing the ability to use those attributes.
In the case of the second example why do you think that the green should not
protrude to the right of the red rule?
The outer DIV that's absolutely positioned has a content area width of 200px,
and a right border edge of 3px. That makes for a total box size of 203px. The
inner DIV has a content area width of 200px and it has right padding of 2px and
left padding of 9px. That makes for a total box size of 211px
That means the child DIV will overflow its parent DIV by 8px. When I look at a
screenshot of the page magnified that's exactly what I see. It's 8 pixels wider
than the parent div.
| Reporter | ||
Comment 3•26 years ago
|
||
1) What you describe makes sense. I reported this bug because of a discrepency
between Moz5 and MSIE 4/5. I guess the bug is with MSIE.
2) The vertical spacing problem (white gap) seems to have been fixed in M12.
Sounds fixed to me.
--Mike
Yes, unfortunately even absolute positioning isn't consistent between the
various browsers.
This is largely because the W3C folks didn't consider the existing browser
implementations when doing the CSS2 spec. I'm trying to get them to revise the
spec to make it more backwards compatible
We strictly implement the spec, whereas IE does not, of course, since their
implementation pre-dated the CSS2 spec
Marking FIXED per your comments
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Updated•26 years ago
|
QA Contact: petersen → chrisd
You need to log in
before you can comment on or make changes to this bug.
Description
•