If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

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

VERIFIED FIXED

Status

()

Core
Layout
P2
normal
VERIFIED FIXED
19 years ago
18 years ago

People

(Reporter: howcome, Assigned: buster)

Tracking

Trunk
x86
Windows 95
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

19 years ago
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

Updated

19 years ago
Assignee: peterl → troy
Component: Style System → Layout

Updated

19 years ago
Status: NEW → ASSIGNED
Priority: P1 → P2

Updated

19 years ago
Assignee: troy → kipp
Status: ASSIGNED → NEW

Comment 1

19 years ago
With your latest changes this can probably be closed
(Reporter)

Comment 2

19 years ago
It still doesn't work on the Sep 20 build.

Updated

19 years ago
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.
(Reporter)

Comment 4

19 years ago
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.

Updated

19 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED

Comment 5

19 years ago
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.

Comment 6

19 years ago
installing myself as QA Contact en masse

Updated

19 years ago
Status: RESOLVED → VERIFIED

Comment 7

19 years ago
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.