316858 - Changing screen resolution mucks up toolbars and menus.

Status: RESOLVED DUPLICATE of bug 315702

(Firefox :: Toolbars and Customization, defect)

Description

[KHOTA]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051107 Firefox/1.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051107 Firefox/1.5

Steps:
1)Right Click on Desktop
2) Click Properties
3) Go to settings
4)Switch screen resolution from 1024 x 768 pixels to 1152 x 864 pixels
5)If already running, Firefox stops displaying the address bar (just a gray area)
Else fire up FF and no Address Bar shows up

Reproducible: Always

Steps to Reproduce:
1.As detailed above
2.
3.
Actual Results:  
Address Bar stopped showing up in the browser

Expected Results:  
Address Bar should show up

Comment 1

[Robin Monks]

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060217 Firefox/1.6a1 ID:2006021705

Changing to an alternate screen resolution makes Firefox go wacky (even if you then switch back to the original, or if you use a game that changes screen resolution), lately, this has produced a ~25px gap at the top of the browser.  (I'll attach a screenshot).

Some tags added and title changed for clarity.

Comment 2

[Robin Monks]

Attachment: Screenshot of problem on trunk builds.

How this problem happens in trunk (happened differently in 1.5 branch, per original reportes description) but they are the same bug.

Comment 3

[Mike Connor [:mconnor]]

Tried on multiple machines, can't reproduce, minusing for now, if MozQA can reproduce on a clean profile please renominate.

Comment 4

[Régis Caspar]

The top gap on theme change can be fixed using (in userChrome.css):
#mainPopupSet { height: 0px !important }

Comment 5

[Wayne Mery (:wsmwk)]

do you still see this in ff 2?

Comment 6

[Wayne Mery (:wsmwk)]

didn't mean to dupe

Comment 7

[Wayne Mery (:wsmwk)]

comment 2 screen shot, which is not exactly the same as described in the original report, is similar to bug 315702. But, report is gone, so duping to bug 315702