Closed
Bug 28194
Opened 25 years ago
Closed 24 years ago
Absolutely positioned text controls overlap
Categories
(Core :: Layout: Form Controls, defect, P3)
Tracking
()
VERIFIED
WORKSFORME
M18
People
(Reporter: ckritzer, Assigned: kmcclusk)
References
()
Details
Overview: In verifying bugzilla #22853, I discovered that on Linux6 one of the absolutely positioned text controls overlaps its neighbor. Steps to Reproduce: 1) Inside firewall, goto above url. Outside firewall, download attached file (courtesy of buster - thanks dude!) 2) Look @ second set of text controls. The left one overlaps the second one. Expected Result: Text controls sit side by side with no overlap Actual Results: One text control overlaps its neighbor Platform found on: - Linux6 2000-02-16-16 Commercial build Additional platforms tested: - MacOS9 2000-02-16-16 Mozilla build (bug does not occur) - Win98 2000-02-16-16 Commercial build (bug does not occur) Additional Info: n/a
Reporter | ||
Comment 3•24 years ago
|
||
nominating for nsbeta2 based on: - severity - visibility - feature (CSS Level 2 Standards Compliance) broken
Keywords: nsbeta2
With the new absolute positioning code checked in the page is laying out correctly Note that Nav 4.x doesn't lay it out correctly
Assignee: buster → troy
Status: ASSIGNED → NEW
Marking WORKSFORME
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 6•24 years ago
|
||
Re-opening bug. Troy, I still see this on Linux6 2000-04-27-09-M16 Commercial build...which build was it working for you on?
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Kevin, sounds like it is a Linux specific problem
Assignee: troy → kmcclusk
Status: REOPENED → NEW
Assignee | ||
Comment 8•24 years ago
|
||
Checked 5/2/2000 Linux commercial build and 5/4/2000 Linux Mozilla build and it is not overlapping. Marking as WORKSFORME
Status: NEW → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → WORKSFORME
Comment 11•23 years ago
|
||
Verfied on build 2001-07-24-06-0.9.2 os:winNT
You need to log in
before you can comment on or make changes to this bug.
Description
•