Closed Bug 32380 Opened 25 years ago Closed 25 years ago

Multiple Plugins for same MIME type

Categories

(Core Graveyard :: Plug-ins, enhancement, P3)

enhancement

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 19118

People

(Reporter: rw263, Assigned: serhunt)

Details

When one has multilple plugins for the same mime type it is often difficult to configure which plugin runs. C(One has to play around with the dates etc...). It would be much easier if the about:plugins was in a drag&drop movable order, or if there where <input type=text> boxes where one could list 1,2,3,4, etc... and then submit it and the plugins would be in the order specificed. These are just two suggestions but there are many ways of handling this with a NICE user interface.
Severity: normal → enhancement
*** This bug has been marked as a duplicate of 19118 ***
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Let me add a comment as to why I marked this a duplicate: Like the submitter suggests, the two solutions presented are just two of the many ways of handling this problem. To clarify, rw263@NYU.EDU 's solution is to put all plugins in a user determinable order and then have mozilla iterate over that list, matching the first plugin which implements the MIME type it's looking for. This however has some disadvantages. Assume plug-ins 1 and 2 both do MIME types A and B, and you want 1 for A and 2 for B. Place 1 first and it will catch both A and B, place 2 first and that will catch both A and B. The solution presented in bug 19118 is to present a list of MIME types with radio buttons for all plug-ins doing that MIME type, which is more generic. Both these bugs however want to accomplish the same: better management of which plug-in is used for what MIME type. Hence I marked this a dup of bug 19118 :-)
I agree Peter, good catch. The orignal bug is "Plug-In Manager for Browser" reading the actual description shows much more specifices about what is wanted then this bug.
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.