Closed
Bug 829209
Opened 13 years ago
Closed 13 years ago
click-to-play doorhanger is annoying and confusing
Categories
(Core Graveyard :: Plug-ins, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 820678
People
(Reporter: douglas.bagnall, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0
Build ID: 20130107224407
Steps to reproduce:
1. Set plugins.click_to_play to true.
2. Visit an internet site that uses plugins.
Actual results:
The pop-up box asks "Would you like to activate the plugins on this page?".
The options given are "activate", "activate all plugins", "always activate plugins for this site", "never activate plugins for this site", and "not now".
Expected results:
The pop-up should not appear. The firefox 17 behaviour, when "click to play" just meant "click to play" was much better.
None of the options appear to match what I want. I want the plugin to be activated when clicked, but the options are "always activate" and "never activate". So I end up going for "not now", even though that is the hardest to get to, and I know it really means "pester me about this forever".
It seems to me that this behaviour is better suited to the "plugins.click_to_play = false" situation.
Updated•13 years ago
|
Component: Untriaged → Plug-ins
Product: Firefox → Core
Comment 1•13 years ago
|
||
@akeybl
Do we have any intention of iterating on this further? The popup is still a bit awkward, perhaps it should only ever auto-trigger for blocklist CTP -- presumably the user knows what's going on when they explicitly enable it.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Hardware: x86_64 → All
Comment 2•13 years ago
|
||
(In reply to John Schoenick [:johns] from comment #1)
> @akeybl
>
> Do we have any intention of iterating on this further? The popup is still a
> bit awkward, perhaps it should only ever auto-trigger for blocklist CTP --
> presumably the user knows what's going on when they explicitly enable it.
This bug should be resolved for the final CTP feature (outside of blocklisting), but we don't really track issues for features behind a pref.
Comment 3•13 years ago
|
||
(In reply to John Schoenick [:johns] from comment #1)
> perhaps it should only ever auto-trigger for blocklist CTP
I think bug 820678 covers this (see bug 820678 comment 23, for instance).
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
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
•