From Bugzilla Helper: User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.1a) Gecko/20020619 BuildID: 2002061908 After getting a new theme the preferences dialog cannot be closed. Reproducible: Always Steps to Reproduce: 1.Open Preferences->Appearance->Themes 2.Click on get new themes 3.Click on deskmod.org Actual Results: There is no way to close the window titled "Deskmod Your Souce for ..." Expected Results: Should be able to close it
WorksForMe using FizzillaCFM/2002062203.
I have just discovered that it depends on your value of Preferences->Advanced->Scripts and Plugins->(Allow web pages to)Open a link in a new window I still think this is a bug: Reproducible: Always Steps to Reproduce: 1.Make sure that Preferences->Advanced->Scripts and Plugins->(Allow web pages to)Open a link in a new window is not checked 2.Restart Mozilla 3.Open Preferences->Appearance->Themes 4.Click on get new themes 5.Click on deskmod.org Actual Results: There is no way to close the window titled "Deskmod Your Souce for ..." Expected Results: Should be able to close it
What build are you using now? Using FizzillaCFM/2002081503, I see an option to "Allow scripts to:" and "Open unrequested windows." in Preferences/Advanced/Scripts & Plugins. Perhaps it's changed recently. Anyway, with that unchecked, this still WorksForMe.
Build 2002081408 for mac osx. Greg: is the deskmod.org page meant to appear in the same window as the preferences or should it open a new window? In my case it appears in the same window which is why I cannot close it.
Julius, when I access Mozilla/Preferences/Appearance/Themes and click "Get New Themes", a new browser window is opened, titled "Download A Mozilla Theme". If I then click DeskMod, another new browser window is opened, showing the DeskMod site. Are you saying these pages are opened in your *Preferences* window? Can you attach a screenshot?
this is my fault. you'll see a message in the jsconsole which shows the problem.
*** Bug 163711 has been marked as a duplicate of this bug. ***
timeless, does your comment 6 mean you confirm this bug? julius, can you still reproduce this problem using a current nightly build?
Greg: I cannot reproduce this with a recent nightly (Mach-O 20030213)
Resolving WFM per comment 9.