Closed Bug 597646 Opened 9 years ago Closed 2 years ago

Dragging multiple extensions into a browser window, only installs the first one

Categories

(Toolkit :: Add-ons Manager, defect)

defect
Not set

Tracking

()

RESOLVED INACTIVE

People

(Reporter: whimboo, Unassigned)

References

Details

(Whiteboard: [AOMTestday][in-litmus-bug-week])

Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b7pre) Gecko/20100917 Firefox/4.0b7pre

When multiple extensions are dragged into a browser window, only the first one will be listed in the software install dialog to be installed. The other ones are getting dismissed.

Steps:
1. Download at least 2 extensions (or themes)
2. Drag both extensions from the file manager
3. Drop them onto a browser window

After step 3 the software installation dialog will popup but only lists the first extension.

That is not a recent regression, and also happens with Firefox 3.6. But I wasn't able to find an already existent bug.
This has always been the case for the browser's content window though it should work on the add-ons manager. I forget where the code is that handles the DnD of xpi's on the content window but it definitely is not in the add-ons manager code.
Duplicate of this bug: 629168
Almost dupe of bug 92737, but there would be some more room to improve after it's fixed.
Depends on: 92737
To be clear, once bug 92737, multiple tabs are opened for each extensions.
and each tab has notification to install the extension.

looks like the notification popup is designed to be able to handle multiple installs at once,
we might be able to merge those notifications into one.
https://groups.google.com/forum/#!topic/mozilla.dev.platform/om5BrXM-Gb8

the feature to install multiple xpis at once seems to be going to be dropped.
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: 2 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.