Closed
Bug 35291
Opened 26 years ago
Closed 26 years ago
[FIX]combo-box in bottom nav frame does not go up if no room down
Categories
(Core :: Layout: Form Controls, defect, P3)
Core
Layout: Form Controls
Tracking
()
VERIFIED
FIXED
M16
People
(Reporter: rb, Assigned: rods)
References
()
Details
(Whiteboard: fix in my tree)
1) Visit the page "http://derstandard.at" if mozilla´s-window is maximised
2) On the bottom (left) there is a "combo-box" ["Express Navigation"]
-> Because the window is maximised it is very hard to choose an item from this
box !
07.04.2000 m15
Comment 1•26 years ago
|
||
Confirmed with the 2000-04-09-08-M15 nightly binary on WinNT 4.0.
This appears to be an edge case (pardon the pun) left over from bug 16152,
"Form Listboxes drawn incorrectly or not at all past canvas edge", FIXED.
The ["Express Navigation"] combobox is in a narrow frame at the bottom of the
page, so when the window is maximized, there is little room for it below, but
plenty of room for it to extend upwards. Currently, it is extending downwards
and being clipped by the edge of the desktop.
Assignee: pavlov → rods
Status: UNCONFIRMED → NEW
Component: GTK Embedding Widget → HTML Form Controls
Ever confirmed: true
OS: Linux → All
QA Contact: pavlov → ckritzer
Hardware: PC → All
Summary: "combo-box" → combo-box in bottom nav frame does not go up if no room down
| Assignee | ||
Comment 2•26 years ago
|
||
I have a fix. It was a small problem in the code that was figuring the absolute
position. It was taking into account if the initial view it checked didn't have
parent then it was suppose to add in the widget offsett.
Status: NEW → ASSIGNED
Summary: combo-box in bottom nav frame does not go up if no room down → [FIX]combo-box in bottom nav frame does not go up if no room down
Whiteboard: fix in my tree
| Assignee | ||
Comment 4•26 years ago
|
||
The GetAbsolutePosition in nsFormControlframe was taking into account if
the frames view had no parent - fixed.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•