Context menus appear partially off-screen after screen resolution decrease

NEW
Unassigned

Status

()

Core
General
--
minor
14 years ago
9 years ago

People

(Reporter: Rolf Campbell, Unassigned)

Tracking

Trunk
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a3) Gecko/20040813
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a3) Gecko/20040813

If the resolution (either vertical or horizontal) is decreased while running
mozilla, and afterwards mozilla is maximized context menus near the display edge
that was changed will appear partially off screen.

Reproducible: Always
Steps to Reproduce:
1. Set resolution to 1024x768.
2. Open mozilla and any web page (www.google.com works).  Minimize mozilla.
3. Change screen resolution to 800x600.
4. Maximize Mozilla
5. Click near the right edge of the mozilla window

Actual Results:  
Context menu partially off the edge of the screen (not visible).

Expected Results:  
Context menu should be fully visible.
Product: Browser → Seamonkey

Comment 1

14 years ago
Confirming with Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a5)
Gecko/20041124. After a resolution change, the previously opened Seamonkey
windows  use the "old" resolution for placing the context menu (the ones opened
after that work fine). This happens when decreasing the resolution (the worst
case) but also when increasing it (try to go from 800x600 to 1024x768 and open
the context menu near the right side of a maximized Seamonkey window).
i can confirm this on my Mozilla:
Mozilla/5.0 (Windows; U; Windows NT 5.1; pl-PL; rv:1.7.5) Gecko/20041204
i can confirm this on my Mozilla:
Mozilla/5.0 (Windows; U; Windows NT 5.1; pl-PL; rv:1.7.5) Gecko/20041204
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/
(Reporter)

Comment 5

13 years ago
Still reproducable in:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050908 Firefox/1.4

No longer reproducable in:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
Component: General → General
Product: Mozilla Application Suite → Firefox

Comment 6

13 years ago
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b5) Gecko/20051013
Firefox/1.4.1

Yes, see this along the right edge of the page as descibed in the steps. 
Confirming.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: context menus appear off screen after resolution decrease → Context menus appear partially off-screen after screen resolution decrease

Comment 7

12 years ago
Note probable relation to bug 258046. This might well be a generic problem with Firefox not (fully) noticing any resolution change (in addition to the descrease reported in this bug).
Assignee: general → nobody
Component: General → General
Product: Firefox → Core
QA Contact: general → general

Comment 8

12 years ago
*** Bug 258046 has been marked as a duplicate of this bug. ***
You need to log in before you can comment on or make changes to this bug.