Closed
Bug 125168
Opened 23 years ago
Closed 11 years ago
Plugins need ability to be disabled on a per window basis
Categories
(Core Graveyard :: Plug-ins, enhancement, P4)
Core Graveyard
Plug-ins
Tracking
(Not tracked)
RESOLVED
WORKSFORME
mozilla1.4beta
People
(Reporter: jud, Assigned: serhunt)
References
Details
(Whiteboard: [PL:BRANCH][Plug-in Mgr])
There are various windows that want to disable the use of plugins within their context. An example of this is Composer windows (see http://bugzilla.mozilla.org/show_bug.cgi?id=88956 ). We currently provide per window functionality toggling via nsIWebBrowserSetup. We then use nsIContentPolicy at callsites to determine whether or not a "load" should proceed. What should probably happen here is that the plugin code queries the content policy via ::ShouldLoad() before loading a plugin. If yes, continue w/ the load, if no, "stop" loading (presumably though not much "loading" has occurred already though and this happens at init time).
Comment 1•22 years ago
|
||
*** Bug 151563 has been marked as a duplicate of this bug. ***
Does this mean I would be able to have a preference to temporarily turn off certain plugins, such as Flash? For example, say I wanted to disable Flash for a while so that I'm not bombarded with ads. But then I want to visit a Flash enabled site. Perhaps the placeholder could say "Get this plugin" or "Enable this plugin" depending. Or should I do an RFE for that?
Updated•22 years ago
|
Priority: -- → P4
Summary: Plugins need ability to be disabled on a per window basis. → [RFE]Plugins need ability to be disabled on a per window basis.
Target Milestone: --- → mozilla1.2beta
Comment 3•22 years ago
|
||
*** Bug 156708 has been marked as a duplicate of this bug. ***
Comment 4•22 years ago
|
||
The plug-ins triage team (av, beppe, peterl, serge and shrir) have reviewed this issue and have made the following determination: This is dependent upon the Plug-in Mgr work, marking dependency
Depends on: 144263
Whiteboard: [PL2:P4]
Comment 5•22 years ago
|
||
[RFE] is deprecated in favor of severity: enhancement. They have the same meaning.
Severity: normal → enhancement
Comment 6•22 years ago
|
||
Could we please change "platform" and "OS" to "all"?
Updated•22 years ago
|
OS: Windows 2000 → All
Hardware: PC → All
Comment: in future it could be important to disable some plugins for safety: I mean the WINE based windows plugins (Crossover) f.i. Quicktime. It should be possible to disable most of the plugins and somtimes to enable someone on secure sites.
*** Bug 179897 has been marked as a duplicate of this bug. ***
Comment 9•22 years ago
|
||
"RFE" in summary is deprecated in favor of severity: enhancement
Summary: [RFE]Plugins need ability to be disabled on a per window basis. → Plugins need ability to be disabled on a per window basis
Comment 10•22 years ago
|
||
moving to 1.4 beta, plug-in branch work
Whiteboard: [PL2:P4] → [PL:BRANCH][Plug-in Mgr]
Target Milestone: mozilla1.3alpha → mozilla1.4beta
Comment 11•22 years ago
|
||
It would be best if the user could enable/disable running of Flush plugins just like it's possible for images (on per site basis).
Comment 12•21 years ago
|
||
I believe it's a duplicate of bug 94035, which has 320 votes and 138 comments as I'm writing this.
Comment 13•21 years ago
|
||
Bug 94035 concerns blocking plug-ins by site; this is about turning off plug-ins by window. It's probably not a dupe, but it could be a WONTFIX if the powers that be decide to approach blocking plug-ins by fixing 94035 instead of this.
Comment 14•21 years ago
|
||
A feature to disable plug-ins on a per-site basis would be greatly appreciated, this would save me from being bombarded by Flash ads and also allow me to watch Flash-enabled sites.
Comment 15•20 years ago
|
||
*** Bug 248534 has been marked as a duplicate of this bug. ***
Comment 16•20 years ago
|
||
Actually, my interest in this capability is completely eliminated with the adblock extension. I would suggest directing folks to try adblock and closing this bug.
Comment 17•20 years ago
|
||
Same here.
Updated•15 years ago
|
QA Contact: shrir → plugins
Comment 18•11 years ago
|
||
You can disable plugin per-docshell.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Updated•2 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•