Closed
Bug 22171
Opened 26 years ago
Closed 25 years ago
[FLOAT] misplaced form widgets inside absolutely positioned DIV
Categories
(Core :: Layout, defect, P3)
Tracking
()
VERIFIED
WORKSFORME
M15
People
(Reporter: 3jrgm, Assigned: buster)
References
()
Details
(Keywords: css2)
Attachments
(3 files)
This bug is split off from bug #21560 (See other related bugs for the same
URL as bug #22168 and bug #14030 -- http://www.espn.com/ has several problems).
This bug addresses a problem with 'misplaced form widgets inside absolutely
positioned DIV' at the top of the viewport. The form widgets in the original
page are partially obscured by another absolutely positioned DIV that overlaps
the first DIV. In the reduced test case (to be attached), I have moved that
second DIV lower on the page. Further comments inside the attachment.
Reporter | ||
Comment 1•26 years ago
|
||
Reporter | ||
Comment 2•26 years ago
|
||
Updated•26 years ago
|
Assignee: karnaze → rods
Comment 3•26 years ago
|
||
Reassigning to Rod.
Comment 4•26 years ago
|
||
Comment 5•26 years ago
|
||
For some reason the form (which is a block frame) is being positioned 17 pixels
lower than it should. Why?
Updated•26 years ago
|
Assignee: rods → troy
Comment 6•26 years ago
|
||
I think it is a generic frame layout problem for these reasons:
1) The form frame is a block frame and it does not do any reflow.
2) If I change the "form" tag to a "p" tag it exhibits the same behavior.
What is interesting is that if I change the "form" tag to a "div" tag it lays
out correctly.
Reassigning to Troy (could be a Kipp line layout issue)
Updated•26 years ago
|
Summary: misplaced form widgets inside absolutely positioned DIV → {css2} misplaced form widgets inside absolutely positioned DIV
mass moving all Kipp's pre-beta bugs to M15. Nisheeth and I will
prioritize these and selectively move high-priority bugs into M13 and M14.
Summary: {css2} misplaced form widgets inside absolutely positioned DIV → [FLOAT] {css2} misplaced form widgets inside absolutely positioned DIV
Comment 9•26 years ago
|
||
Migrating from {css2} to css2 keyword. The {css1}, {css2}, {css3} and {css-moz}
radars should now be considered deprecated in favour of keywords.
I am *really* sorry about the spam...
Updated•25 years ago
|
Summary: [FLOAT] {css2} misplaced form widgets inside absolutely positioned DIV → [FLOAT] misplaced form widgets inside absolutely positioned DIV
Comment 10•25 years ago
|
||
This has now been fixed. The problem was that FORM (and P) elements had 1em
top margin, which is not backwards-compatible. This has now been removed, and
FORM elements only have 1em bottom margin.
Marking WORKSFORME. It's really a DUP of the "form elements have non backwards
compatible margins" bug but I can't remember that bug's number off hand.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 11•25 years ago
|
||
Yep. That would be the fix per discussions on 16253 "{compat} FORM margins not
backwards compatible". Marking VERIFIED. Thanks.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•