Closed
Bug 345703
Opened 19 years ago
Closed 19 years ago
When the downthemall-manager extension is the only open window the menubar is unresponsive
Categories
(Firefox :: General, defect)
Tracking
()
VERIFIED
INVALID
People
(Reporter: andy, Unassigned)
Details
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; chrome://navigator/locale/navigator.properties; rv:1.9a1) Gecko/20060722 Camino/1.2+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-GB; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4
When the downthemall extension is the only open window the menubar is unresponsive, short keys are also broken.
you have to close the dta-manager window to get functionality back. this sucks if you are in the middle downloading a large unresumable file and want to continue browsing the web as dta will stop the download if you close the dta manager window!
Reproducible: Always
Steps to Reproduce:
1. open dta manager, close other firefox windows
2. attempt to use the firefox menubar items
3. or short keys, i.e. cmd-n for a new window.
Actual Results:
either no menubar items are visible, or if they are blank menu pull-downs are displayed.
shortcut keys do nothing. cmd-n will not open a new window.
Expected Results:
firefox menubar items should be displayed and be functional while dta manager is open. open new window should open a new browser window. cmd-n should open a new window, etc.
should mention that this may be related to bug <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=239218">239218</a>.
i'm seeing this happen on 1.5.0.5 -> the latest 2.0 branch nightlies.
Version: unspecified → 2.0 Branch
Comment 2•19 years ago
|
||
Bugs in extensions are normally marked INVALID and the reporter is asked to contact the extension author for a fix.
It could be a Firefox bug, but bug 239218 was fixed before 1.5 was released and is likely to be unrelated, unless it has regressed. Do you get the same behaviour with dialogs created by Firefox itself ?
Comment 3•19 years ago
|
||
This is an extension bug, comment #2 is exactly right, you should attempt to contact the extension author.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
Updated•19 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•