Closed
Bug 761840
Opened 12 years ago
Closed 7 years ago
Firefox with click_to_play should let me always allow/block plugins for a whole domain
Categories
(Core Graveyard :: Plug-ins, enhancement)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: ronan, Unassigned)
References
Details
Attachments
(1 file)
(deleted),
image/png
|
Details |
*Description* Currently, with plugins.click_to_play=true, I can instruct Firefox to always allow plugins like Flash on a site (http://abc.com). Unfortunately, the feature is restricted to that subdomain, and I cannot always allow plugins on the whole domain (http://*.abc.com). *Use case & rationale* 1. I visit http://rien.bandcamp.com (great music!), and tell Firefox to always allow Flash 2. Later on, I visit http://manmachine.bandcamp.com (great music too!), but again I have to activate Flash here. 3. Etc. My point is that some domains (e.g. music/video sites like bandcamp.com, soundcloud.com, etc.) still use Flash on all their subdomains. It's a pain to have to enable it for each individual page, even though I know I trust bandcamp.com and know I want Flash on all bandcamp.com sites. It has obvious security drawbacks, but since the feature is already geeky and not-so-discoverable, we can probably expect the user knows what a domain is, and what the consequences of a domain-wide exception are. *Notes* - FlashBlock support whitelisting by domain. So to a FlashBlock users eyes, that's a functional regression. - Quick UI mockup attached. Thanks for the work
Updated•12 years ago
|
Blocks: 711618
Status: UNCONFIRMED → NEW
Component: General → Plug-ins
Ever confirmed: true
Product: Firefox → Core
QA Contact: general → plugins
Version: unspecified → 14 Branch
I would like fine grained control. Just because I allow http://rien.bandcamp.com does not mean I automatically want to allow http://manmachine.bandcamp.com though I admit that there will be time when I want to. What I propose is Allow on bandcamp.com Allow on http://manmachine.bandcamp.com Much like what Adblcok Plus allows me to do with filters. Don't tie the users hands!
@hugh, using the existing permissions model (favicon left of url-->more info-->permissions) would take care of the use case you explained. CSLite for example exposes this model.
Comment 3•7 years ago
|
||
Resolving old bugs which are likely not relevant any more, since NPAPI plugins are deprecated.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
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
•