287856 - Options & Sanitize Dialog Boxes In Firefox 1.0+ Are Not Visible

Status: RESOLVED INVALID

(Firefox :: Menus, defect)

Description

[Brian Moura]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050325 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050325 Firefox/1.0+

After installing Firefox 1.0+ nightly build 3/25/05, when the menu TOOLS,
OPTIONS or TOOLS, SANITIZE are selected, the dialog box is not visible.  


Reproducible: Always

Steps to Reproduce:
1. Install Firefox 1.0+
2. Open Firefox 1.0+
3. Select TOOLS, OPTIONS or TOOLS, SANITIZE


Actual Results:  
Rather than the Options or Sanitize dialog box appearing, the current screen/web
page remains.  The only thing that Options or Sanitize does to change the
current screen/web page is it adds the dialog box headings (GENERAL, PRIVACY,
CONTENT, TABS, DOWNLOADS, ADVANCED) and the OK and CANCEL radio buttons to the
current screen/web page.


Expected Results:  
The OPTIONS or SANITIZE dialog box should have appeared in place of the current
web page/screen.

Comment 1

[José Jeria]

WFM: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050326
Firefox/1.0+

Did  you try to start in safe mode?

Comment 2

[Brian Moura]

When starting Firefox in Safe Mode (all extensions and themes disabled), the
dialog boxes appear as expected.

However, this generates another problem - an alert stating "ALERT. The file
/D:/Program Files/Firefox 1.0/Files/Firefox cannot be found. Please check the
location and try again."

Comment 3

[Brian Moura]

After further testing, I've discovered that the Options & Sanitize dialog boxes
will display in Firefox 1.0+ with the default Theme active - but not when any
optional themes - such as Qute 3, Qute Retro 2.74, Platinum 1.01, Silver Skin,
etc. are used.

So it would appear that the interaction between the custom themes and the new
dialogs are the issue here.

Comment 4

[Simon Paquet [:sipaq]]

Apparently these 3rd party themes haven't yet been updated for the new stuff on
the trunk. 

-> Not a bug in Firefox