Closed Bug 299956 Opened 20 years ago Closed 19 years ago

FIELDSET tag children's margins collapse

Categories

(Core :: Layout, defect)

1.8 Branch
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 205732

People

(Reporter: keithjclark, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 When specifiying margins for children of a FIELDSET they collapse to nothing. Opera and IE both behave as expected. If you replace the FIELDSET tag with DIV the page renders correctly. Reproducible: Always Steps to Reproduce: Use this HTML: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <title>Bug Test</title> </head> <body> <fieldset> <h1 style="margin:0.5em 0 2em 0"><textarea cols="40" rows="5">Test</textarea></h1> </fieldset> <fieldset> <h1 style="margin:0.5em 0 2em 0"><textarea cols="40" rows="5">Test</textarea></h1> </fieldset> <fieldset> <h1 style="margin:0.5em 0 2em 0"><textarea cols="40" rows="5">Test</textarea></h1> </fieldset> </body> </html> Actual Results: My 0.5em top and eem bottom margin evaluated to 0 Expected Results: Applied the margin ala the DIV tag
Related to Core bug 205732?
(In reply to comment #1) > Related to Core bug 205732? Yes - its similar but that bug document margin-top. This is all margins for any block tag inside a FIELDSET.
Component: General → Layout
OS: Windows XP → All
Product: Firefox → Core
QA Contact: general → layout
Hardware: PC → All
Version: unspecified → 1.8 Branch
It's basically the same issue as bug 205732, which is now fixed in current branch and trunk builds. *** This bug has been marked as a duplicate of 205732 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.