Closed Bug 539486 Opened 16 years ago Closed 16 years ago

Clicking Options for an extension sometimes causes the Add-ons Manager window to freeze

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 529655

People

(Reporter: atb12345, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2) Gecko/20100105 Firefox/3.6 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2) Gecko/20100105 Firefox/3.6 Clicking Options for an extension sometimes causes the Add-ons Manager window to freeze while "No chrome package registered for chrome" is displayed in the Error Console. The Add-ons Manager no longer responds to mouse clicks or key presses. It can be eliminated only by killing Firefox from the XP Task Manager. Reproducible: Always Steps to Reproduce: 1. Create a new profile with Fx 3.6 RC1 2. Install BlockSite 0.7.2 from https://addons.mozilla.org/en-US/firefox/addon/57211 3. Open the Add-ons Manager with Tools > Add-ons > Extensions 4. Click on the BlockSite Options button Actual Results: No Options dialog pops up. The Add-ons Manager cannot be closed. Pressing Esc or Alt-F4 has no effect. Clicking the close button has no effect. The Error Console displays "No chrome package registered for chrome://blocksite/content/BlockSitePrefs.xul" The Firefox browser window can be closed with File > Exit, but the Add-ons Manager persists and firefox.exe remains in the Task Manager. I had to kill Firefox from the Task Manager to kill the frozen Add-ons window. Expected Results: The BlockSite Preferences dialog pops up. The dialog can be dismissed by pressing Esc or Alt-F4 or by clicking OK, Cancel, or the dialog's close button. The Add-on Manager can be then be closed. Problem also exists in Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2pre) Gecko/20100112 Namoroka/3.6pre and Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.3a1pre) Gecko/20100112 Minefield/3.7a1pre Problem does not exist in Fx 3.5.7.
I confirmed on Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2pre) Gecko/20100114 Namoroka/3.6pre ID:20100114050231 This expansion does not include chrome.manifest. But optionsURL is defined in install.rdf.
What is happening here: extension manager tries to open extension options as a modal dialog. This fails (optionsURL given is wrong) - but we still end up with a modal dialog, a transparent one. For the user it looks like the extension manager window is broken. I don't think this can be really fixed on the extension manager's side (even if the dialog is opened in non-modal mode, we still end up with a transparent window that we certainly don't want). So this is a core bug, this window shouldn't be opened in the first place.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.