Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Firefox 14 plugin click to play not working well with YouTube

  • 12 replies
  • 76 have this problem
  • 6 views
  • Paskiausią atsakymą parašė AliceWyman

more options

With the new plugin click to play setting set to true, clicking the full screen or larger window box for a YouTube video does nothing. If I set it back to false, those controls work. Something about that setting is messing up YouTube video controls.

With the new plugin click to play setting set to true, clicking the full screen or larger window box for a YouTube video does nothing. If I set it back to false, those controls work. Something about that setting is messing up YouTube video controls.

All Replies (12)

more options

Ok, I'm going to have you try a few things, this may just be a bug in Firefox and/or Flash that we have to file.

First, try to reset Firefox. Refresh Firefox - reset add-ons and settings. This simple step will eliminate many Firefox problems with only one click.

After doing that, see if you can get Youtube to work or not.

more options

I have since found out that this is a recognized bug in Mac Firefox. It is not resolved yet.

more options

same here. resetting click to play to False alleviates the problem.

btw, using Windows 8 Release Preview. Firefox 13 have no problem.

Modified by rino19ny

more options

Related bug reports:

  • Bug 775709 - Mac Firefox plugin.click_to_play enabled interferes with video controls

... which is a duplicate of:

  • Bug 751809 - click does not work on a plugin content when a plugin is just activated

Just so you know, the new "Click-to-Play" feature for plugins is a work in progress. More info/discussion here: https://support.mozilla.org/forums/contributors/708518 Problems ahead with "plugins.click_to_play"?

more options

Same problem, but happen when i instaled Google Chrome (Happend twice, 2 diferent computers)

more options

Alice,

If that click-to-play is buggy (and known to be so), why put it into a final release? That kind of thing does not make a good impression.

more options

@ finitarry,

You asked, If that click-to-play is buggy (and known to be so), why put it into a final release? That kind of thing does not make a good impression.

I can't answer you but you could ask that question in the SUMO Community discussions forum, in the thread that was already started:

more options

Ok, thanks, I did that. The audio placeholder cuts off the text message as well, so that is also buggy.

more options

Opt-in activation for plugins is targeted for Firefox 16 and to get it on 14 you need to go out of your way and change a preference in about:config so I'd contend it is "put it into a final release".

Testing of the feature is appreciated and, of course, feel free to file bugs for any issues encountered.

more options

Besides the two bugs shown above, there are some other plugins.click_to_play bugs being discussed here:

https://support.mozilla.org/forums/contributors/708518 Problems ahead with "plugins.click_to_play"?

Silverlight embedded videos not displaying a "click here to activate" button is one bug; direct links to files that are set to open with a plugin not displaying any content when clicking the "activate" button (such as .pdf -> Adobe acrobat plugin or mov -> QuickTime plugin) is another.

more options

I have a similar problem with google music. when click to play is active i try to listen to music and i get an error because the plugin failed to load. There is nothing to "click to play" as it were. it'd be nice if there was a notification to enable plugins on a site with hidden plugins. thank you :D

oh and pandora.com does the same thing.

Modified by sebanisu

more options

sebanisu, You're right about pandora and google msic not working with click-to-play enabled. You should reset the plugins.click_to_play preference back to "false" in about:config, since this is an experimental feature that is still being "debugged".

Since this is not a "support" issue but rather feedback about a new feature that is still undergoing testing, I'm locking this thread. See this contributors forum discussion for more information: