Closed Bug 267120 Opened 20 years ago Closed 20 years ago

Dual screen with different resolutions gives problems with listbox of a select

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 245418

People

(Reporter: roy_dam, Assigned: bugzilla)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3

On a dual screen computer with screens with different resolutions when using
Firefox in the screen with the lowest resolution, the size and position
(above/beneath) of the listbox of a select is calculated wrong. This is because
of that the desktop size is used for the calculation instead of screen size of
the screen where Firefox is used. The consequence of this is that sometimes a
part of the listbox is outside the screen (listbox is to large). Also sometimes
the listbox is diplayed above the select when is should be displayed beneath the
select.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.
dupe of bug 245418 ?
No, this is not a duplicate of bug 245418.
The size of a list(box) of a html select is sometimes calculated wrong. When
Firefox is used in the screen with the lowest resolution, the list is displayed
in that screen. But the size of the list is calculated according to the size of
the largest screensize (other screen) or desktopsize. The consequence of this is
that sometimes a piece of the list is outside the screen (depends on the
position of the select on the screen). Also the decision to display the list
above/beneath the select itself (wherever the space is the largest), is
sometimes wrong.
This is a dupe of bug 245418. The patch in that bug should take care of all of
the issues you describe. Reopen if that is not the case.

*** This bug has been marked as a duplicate of 245418 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.