Closed Bug 808 Opened 26 years ago Closed 26 years ago

padding and borders don't work on HTML and BODY elements

Categories

(Core :: Layout, defect, P2)

x86
Windows 95
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: howcome, Assigned: buster)

References

()

Details

Setting padding and/or margins on HTML/BODY elements don't have any effect (with the exception of padding on BODY elements). For a test case, See issue #2 in the attached UR
Assignee: peterl → troy
Component: Style System → Layout
Status: NEW → ASSIGNED
Priority: P1 → P2
Assignee: troy → kipp
Status: ASSIGNED → NEW
With your latest changes this can probably be closed
It still doesn't work on the Sep 20 build.
Status: NEW → ASSIGNED
Some of this (at least margins on BODY) was working for a while, but now it doesn't work again, so I'm commenting here. The idea of margin and border (and maybe padding) on HTML is questionable, but BODY margins and borders should definitely be supported, and the margins (including the expanded bottom margin of short pages) should be given the background-color of HTML, but if that is not defined, then the background-color of BODY.
It seems like the CSS WD will reach consensus on: - margin/border/padding are optional on the HTML element - margin/border/padding are required on tht BODY element The fact that margins on BODY are not honored is currently the #1 reason why I can't showcase nglayout more than I do.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
I just added code to support body margins (padding/border were already there). Note that if the body ends up scrolling, the display won't yet look as it should because it's still the case that the HTML object is the root frame instead of the immediate child of the root frame (this is where we will be placing the overflow: auto scrolling property). Bug #677 covers that problem so I'm closing this one.
installing myself as QA Contact en masse
Status: RESOLVED → VERIFIED
VERIFIED fixed for Win32 199952109 yes i know it was fixed long, long ago
You need to log in before you can comment on or make changes to this bug.