Closed Bug 69215 Opened 25 years ago Closed 24 years ago

Browser should remember when I don't want to download a plug-in

Categories

(Core Graveyard :: Plug-ins, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 61103
Future

People

(Reporter: zackw, Assigned: chrisn)

References

()

Details

The above site uses Shockwave which I do not have installed. Mozilla asks me if I want to download the plug-in every time I load the site. It should remember that I already said NO and not bother me again.
Reporter: Which Build are you using ? This should be a dupe of bug 64821 *** This bug has been marked as a duplicate of 64821 ***
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
This is not the same as bug 64821. That bug describes a nonfunctional "don't show this box again" checkbox. The popup I get does not have any such checkbox. It just says "This page contains information of a type (application/x-shockwave-flash) that can only be viewed with the appropriate plug-in. Click OK to download plugin. [OK] [CANCEL]" Oh, and the window title bar says "default plugin". I'm using Mozilla 0.8, build id 2001021503, i686-pc-linux-gnu talkback binary, but I doubt this would be platform-specific.
This is a platfom specific bug. Looks like a job for the default plugin. On Windows it (the default plugin) keeps a track of mimetypes already seen and by default does not show up second time. Changing platform to Linux. cc'ing serge as he seems to have a momentum on fixing the default plugin problems on Linux.
Confirming ==> new
Status: UNCONFIRMED → NEW
Ever confirmed: true
This appears to be a duplicate of bug 61333, or at least a related bug.
The dialog should display at least once per session if I continue visiting the site, unless I do something to say "don't show this dialog again for mimetype foo". At some point, the Windows version would never show again after hitting "cancel" once, which is silly because "cancel" shouldn't have any permanent effect.
This has been well thought and taken by consensus of several people. It is not as 'silly' as it might seem. Imagine a user who just doesn't care about all those modern gimmick like nice but senseless plugins and cares about real content only. Why to bother him every time he hits his favourite page? The semantics and connotation of the Cancel button in this case is intuitively 'Please don't annoy me' which I agree somewhat contradicts to the common paradigm of what the Cancel button should do, but perfectly meets this bug report summary line.
Assignee: av → chrisn
Target Milestone: --- → Future
Marking future and reassigning to chrisn.
*** Bug 90051 has been marked as a duplicate of this bug. ***
*** Bug 90207 has been marked as a duplicate of this bug. ***
I think this should be done through a checkbox and not by clicking Cancel. Imagine if the user wants to download the plugin, but not now. They would have to click Cancel but then wouldn't be asked next time. In the same vein, when the user chooses not to accept a cookie, they are still asked next time. They have to check a box to be never asked. It might also be a good idea to have a list of don't-ask-me MIME types and allow users to remove a MIME type from the list.
*** Bug 104648 has been marked as a duplicate of this bug. ***
How is this different from bug 61103? It's worded differently, but it seems like the same basic problem, right?
Hmm, yes, that does seem to be the same bug, reported for Mac instead of Linux. I get the impression that only the Win32 default plugin is clever enough to remember what plugins the user has already rejected. Is this correct?
Depends on: 83754
Same bug. *** This bug has been marked as a duplicate of 61103 ***
Status: NEW → RESOLVED
Closed: 25 years ago24 years ago
Resolution: --- → DUPLICATE
mass duplicate verifications . For filtering purposes, pls use keywd "massdupverification"
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.