Closed
Bug 137514
Opened 23 years ago
Closed 23 years ago
[RFE]pref. to prompt before allowing a plugin to execute
Categories
(Core Graveyard :: Plug-ins, enhancement, P4)
Core Graveyard
Plug-ins
Tracking
(Not tracked)
VERIFIED
WONTFIX
Future
People
(Reporter: mcs, Assigned: rubydoo123)
Details
(Whiteboard: [Plug-in Mgr])
It would be very nice to have a per-plugin preference which, if enabled, would
cause the browser to prompt the user before allowing a specific plugin to run.
That way, the user could leave the Java or Flash plugin installed, but the
plugins would not be loaded when not really necessary (a lot of sites use Flash
animations, but I rarely care to see them; on the other hand, sometimes I do
want to see them).
One problem might be that installed plugins probably cause the browser to send
additional HTTP Accept: headers (for the additional MIME types supported by a
plugin). If the preference I suggest were implemented, the browser would claim
to support certain MIME types but then ignore them, and some web sites might be
written to conditionally use something like Flash. But this is speculation; I
don't know exactly how plugin loading occurs.
Comment 1•23 years ago
|
||
Will this be handled by the 'plugin manager' bug?
Assignee | ||
Comment 2•23 years ago
|
||
so, are you kind of thinking the pref to act like the image pref for don't
download images?
Reporter | ||
Comment 4•23 years ago
|
||
To answer beppe: sure, plugin preferences that worked like those for images
would be very useful. The confirm dialog should tell the user which plugin will
be loaded though (so I know if I am saying yes to Flash vs. Java vs. a TIFF
viewer plugin).
Assignee | ||
Comment 5•23 years ago
|
||
That sounds interesting, setting to future and P4, will readdress this request
when we review all enhancement requests.
Status: NEW → ASSIGNED
Priority: -- → P4
Summary: pref. to prompt before allowing a plugin to execute → [RFE]pref. to prompt before allowing a plugin to execute
Target Milestone: --- → Future
Assignee | ||
Updated•23 years ago
|
Whiteboard: [Plug-in Mgr]
Assignee | ||
Comment 6•23 years ago
|
||
The plug-ins triage team (av, beppe, peterl, serge and shrir) have reviewed this
issue and have made the following determination:
We will be doing a variant of this request, we will be following current image
implementation: using content policy.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → WONTFIX
Reporter | ||
Comment 7•23 years ago
|
||
Is there a bug that tracks the feature you do plan to implement? I assume
"content policy" means the ability to block some sites, etc. like you can do for
images?
Assignee | ||
Comment 8•23 years ago
|
||
oh, sorry I thought I entered the bug numbers: bug 44973 and bug 144262
The last one should read ' bug 144263 '.
Comment 10•23 years ago
|
||
marking verif, pls reopen stating a reason, Thx!
Status: RESOLVED → VERIFIED
Comment 11•22 years ago
|
||
See also bug 169330, replace usually-unwanted plugins (e.g. Flash) with "click
here to run the plugin". That's similar to this solution but doesn't require a
prompt.
Updated•3 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•