296773 - Freeze if I click options in extension manager IF a disabled entension is highlighted (not compatiable with deer park 1.0+)

Status: RESOLVED DUPLICATE of bug 284515

(Toolkit :: Add-ons Manager, defect)

Description

[Anko]

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

I clicked 
Then I highlighted Adblock (which has been disabled because it's not compatible
with deer park 1.0+)
then i clicked options, and that 'extensions' window has frozen, not accepting
any input, even to the maximise/minimise/close buttons.  The rest of firefox
(dear park) is fine.

Reproducible: Always

Steps to Reproduce:
1.Click Tool, Extensions.
2.Highlight an extension that has been disabled.
3.Click the options button.

Actual Results:  
The extensions window has frozen, not allowing any more mouse or keyboard input,
including freezing the minimise, maximise and close buttons.

Expected Results:  
The Extension window should not have frozen, allowing me to close it.

Comment 1

[Anko]

Sorry, I was just testing it to narrow it down, and it seems that somehow this
bug has changed behaviour slightly.

Now i have to;
1) open extension manager
2) click on a disabled extension
3) click update - it will say no updates available
4) click on options (notice the options button for the disabled extension is now
clickable

It will now freeze.

Comment 2

[Anko]

Okay i just tested it some more, and now i can't even reproduce it. I have
reproduced it 8 times in the past.

Now the options button does not get enabled after i click update.

This is pure speculation, but possibly it was that those extensions were getting
updated, but saying that they weren't, and that's why the options window got
reenabled, but since the extension wasn't enabled, it caused a freeze?

Appologies for the bugspam.

Comment 3

[Robert Strong (they/them - no direct email)]

I believe this has already been fixed and that this bug is a duplicate of bug
284515 which landed after the Deer Park release.

Comment 4

[Anko]

*** This bug has been marked as a duplicate of 284515 ***