Closed Bug 522904 Opened 15 years ago Closed 6 years ago

Blocked addons "More info" link opens a new browser window as modal [blocklist]

Categories

(Toolkit :: Add-ons Manager, defect)

x86_64
Windows Vista
defect
Not set
normal

Tracking

()

RESOLVED INACTIVE

People

(Reporter: ws.bugzilla, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 (.NET CLR 3.5.30729)

See STR

Reproducible: Always

Steps to Reproduce:
The window that tells me about add-ons that have been blocked ("Add-ons may be causing problems") has a "More information" link. Click it. A new firefox window is opened.

Actual Results:  
It is now impossible to activate or move the "Blocked addons" window until I've closed the new firefox window.

Expected Results:  
Ideally the "More info" window should reuse an existing firefox window, just like any other link I open from another application.

The URL that the "More information" takes me to reports an invalid security certificate. I was taken to "https://en-gb.www.mozilla.com/en-GB/blocklist/". This said that the cert is invalid because it's only for "*.mozilla.com", which could be a separate (probably known) bug.
Component: General → Add-ons Manager
Product: Firefox → Toolkit
QA Contact: general → add-ons.manager
Cert part is bug 505031 and related.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Blocked addons "More info" link opens a new browser window as modal → Blocked addons "More info" link opens a new browser window as modal [blocklist]
Severity: minor → normal
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.