Closed
Bug 40644
Opened 25 years ago
Closed 24 years ago
[Fix]Page layout very incorrect after using "reset" type button
Categories
(Core :: Layout, defect, P3)
Tracking
()
VERIFIED
FIXED
M16
People
(Reporter: selmer, Assigned: rods)
References
()
Details
(Whiteboard: [nsbeta2+] fix in my tree)
Go to the bug and just scroll down and click on the button labeled "reset".
Look at the page layout that results. Many things are out of place like labels
drawing on top of edit fields etc.
The page source says this button is <input type="reset" value="reset"> so maybe
the result is related to that somehow.
Reporter | ||
Comment 1•25 years ago
|
||
build 2000-05-25-08 on NT.
Comment 2•24 years ago
|
||
Re-assigning to pollmann as part of triaging clayton's bug list.
Assignee: clayton → pollmann
Comment 3•24 years ago
|
||
This seems to be a problem with reflow of combo boxes inside of tables. I put a
reduced test case up at:
http://blueviper/bugs/odd.html
The basic problem is that the first time the page is layed out, the combo box
lays out the width of the longest option. The second time (press reset button),
the combo takes only the width of the selected option, and the drop down button
does not draw.
Assignee: pollmann → rods
Comment 4•24 years ago
|
||
Nom. nsbeta2 as this is interfering with use of Bugzilla form, recc. nsbeta2,
recc. nsbeta2+ [some lenient date-], falling through to hard stopper for
nsbeta3. This is b.c. with basic HTML 3.2 form elements--we MUST FIX THIS before
rtm.
Assignee | ||
Updated•24 years ago
|
Status: NEW → ASSIGNED
Summary: Page layout very incorrect after using "reset" type button → [Fix]Page layout very incorrect after using "reset" type button
Whiteboard: [nsbeta2+] → [nsbeta2+] fix in my tree
Assignee | ||
Updated•24 years ago
|
Target Milestone: --- → M16
Assignee | ||
Comment 7•24 years ago
|
||
fixed
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Comment 8•24 years ago
|
||
This problem is not occuring for me with the June 19th build (2000061908).
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•