Closed Bug 7721 Opened 26 years ago Closed 25 years ago

Placement problem with first paragraph

Categories

(Core :: Layout, defect, P3)

x86
Windows NT
defect

Tracking

()

VERIFIED INVALID

People

(Reporter: talvola, Assigned: buster)

Details

The bottom frame of this web site: http://home.earthlink.net/~mikieat/ doesn't display as it does with Netscape 4.5. The buttons appear too far down in the frame and get chopped off halfway. Didn't see anything obvious in the source that seemed unusual.
Summary: Images in frame not displayed correctly. → Images in frame not displayed correctly in Mozilla M6.
Assignee: rickg → karnaze
Chris - this is either a frameset bug or a layout bug. Please take a quick look to diagnose.
Summary: Images in frame not displayed correctly in Mozilla M6. → Placement problem with first paragraph
No, this is a problem with <p>. It occurs on pages without frames as well The first paragraph on the a page is misplaced. It is placed at one row's height from the top of the frame if it is more than the marginheight. Simple example (I used the style attribute to make the problem better visible.) ---- <html> <body marginheight=0 topmargin=0> <p style="background-color:red">some text</p> </body> </html> ---- Additional comments: - I found no placing problem when <p> is used in a table cell... - There is also a placing problem with the last paragraph on the page, I can send a testcase for that, and/or file a separate bug. I'm changing the summary line.
Assignee: karnaze → kipp
Reassigning to Kipp based on previous comments.
If you change that p to div or add "margin:0" to the style attribute, the 1em margin of the p element should go away.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
This is not a bug. The Mozilla UA stylesheet says that: P { margin: 1em 0; } Mozilla is correctly following that. If you don't want the top margin, then use CSS to set margin-top on the first p to 0. This can be done, if you are using strict HTML4, like this: body > p:first-child { margin-top: 0em; }
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.