Closed Bug 253274 Opened 21 years ago Closed 20 years ago

menus and tooltips are unaware of xinerama

Categories

(Firefox :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED EXPIRED

People

(Reporter: slicks+mozilla, Assigned: bugzilla)

References

()

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040719 Firefox/0.9.1 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040719 Firefox/0.9.1 On http://slicks.ulyssis.org/firefox-xinerama.png a desktop is displayed with 2 heads using Xinerama. The borders of the heads are shown in red. As there are two different screen resolution, there's a blind rectangle in the lower-left corner. That area isn't mapped to a physical screen. Applications using GNOME or KDE libs use information from Xinerama to avoid menus being split over several heads. By doing this, they also avoid showing anything on that blind area. Firefox doesn't seem to do that. On that screenshot you can see that a part of the popup will be invisible to the user. Same thing for tooltips. This screenshot has been taken with fluxbox, but the problem also occurs in KDE. Reproducible: Always Steps to Reproduce: 1. Put firefox near the border of a head which is not a border of the whole desktop. 2. Open the context menu/tooltip near that border. Actual Results: The menu/tooltip is split over several heads, or is only partially shown. Expected Results: The menu/tooltip should be repositioned to fit inside the current head. Tested with Fluxbox CVS 20040726 and KDE 3.1.2
I can confirm this on Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041024 Firefox/1.0 running KDE 3.3.1 on Xorg 6.8.1. However, Mozilla 1.7.3 works just fine, shoving menus and tooltips over so they remain on only one screen at a time.
Confirmed on Fedora Core 3, running the Xorg X server. As noted, Seamonkey does not have this problem.
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.