I notice you have the NoScript extension installed. Can you double-check when you're on a problem page that you've allowed enough scripts on the NoScript menu? Note that sometimes video content will be hosted on a different server from the one shown in the address bar -- you may need to allow more than one server in order to get things to run.

Sometimes after a Firefox update, an extension will stop working normally. Could you test in Firefox's Safe Mode.? That's a standard diagnostic tool to bypass interference by extensions (and some custom settings). More info: Diagnose Firefox issues using Troubleshoot Mode.

You can restart Firefox in Safe Mode using

Help > Restart with Add-ons Disabled (Flash still works in Safe Mode)

In the dialog, click "Start in Safe Mode" (not Reset)

Any difference?

I went to NoScript and told it to temporarily all scripts on this page. Instead of showing the video it was still telling me to Get Adobe Flash Player. So I did the Safe Mode thing. Now YouTube videos will at least play. But that one video on The Blaze site still tells me to get Adobe Flash Player. Now I have to repeat the process, that seems to be getting done on a more regular basis every time Firefox updates, of going through and trying to find which one of my add-ons might be causing this issue. This is getting to be a ridiculous problem, and very time consuming. I guess the best thing might be to go back to IE as my default.

Hi rocmar62, if sites can use the Flash Player in Safe Mode, one reasonable deduction is that one of your add-ons -- maybe not NoScript -- is interfering with sites using the player. Many sites use multiple domains (for example, youtube.com uses ytimg.com, facebook.com uses fbcdn.net). If you have extensions that block "third party" cookies or otherwise try to filter secondary servers sites use, those might also be causing this issue.

It could take some time to track down, but as a first step, try disabling ALL nonessential or unrecognized extensions. By nonessential, I mean you could live without it for 24 hours. To do that, open the Add-ons page using either:

• Ctrl+Shift+a
• orange Firefox button (or Tools menu) > Add-ons

In the left column, click Extensions.

Usually a link will appear above at least one disabled extension to restart Firefox. You can complete your work on the tab and click one of the links as the last step.

Any difference?

You might also need to change your cookie setting to allow third party cookies in the Privacy options.

orange Firefox button (or Tools menu) > Options > Privacy

The biggest issue here is that, so often, Firefox updates "break" its usage. I just don't understand that. As a long time user of NoScript - and lets use YouTube as the example here - I already have all those settings for YouTube set in NoScript. I already have all those items set to be allowed on YouTube, yet one evening, before I go to bed, I allow Firefox to be updated. The next day I can no longer watch a single video on YouTube. WHY???? The only thing that has changed was the Firefox update. I shut my computer down after the update completed, and restarted it the next morning. Nothing happened to it overnight. There have not been any recent updates of any kind, and there have been no recent new installations. Yet Firefox is "broke" when it comes to YouTube. WHY?????? And this happens more often than not. Why??? This, along with the fact that some recent browser comparisons show that IE is a now a little faster than Firefox are really making it hard to keep using Firefox. Those comparisons are also showing that for all practical purposes they are pretty much equal in regard to Safety. But to have to go through the process of figuring out why your browser is broken due to the most recent update practically every time an update comes, makes it very cumbersome to use. I've enjoyed using Firefox, every since its very, very early versions. I haven't even minded the fact that oftentimes it told me that one or more of my extensions were no longer compatible with it, and I could no longer use it, while hopefully someone upgraded so that it was compatible. Upgrades, especially major ones, seem to be coming more quickly any more. And maybe that is the major issue behind "breaking" it for users. I haven't had any messages over the last several upgrades that I have incompatible extensions. In fact, over the last several upgrades I don't even remember it saying that it (the upgrade) is checking my extensions for compatibility???? This makes it impossible for me to say that My Problem Was Solved until I see what the next upgrade happens!!!

Hi rocmar62, a lot of site breakage issues are identified during pre-release testing, and obviously many beta users would be visiting Youtube, but one of the strengths/weaknesses of Firefox is extensibility, with the result that there are at least thousands, maybe tens of thousands of unique combinations of add-ons and customizations.

I can't tell from your last reply whether you were able to figure out the problem in this case, but your input on that may help the next user searching for the same solution, so please report your findings when you can.

Hi rocmar62, I missed that Firefox 25 turned on "click to play" as the default behavior for plugins. I assume you prefer to have Flash run automatically if you've approved the site in NoScript.

In case this change corrupted your setting for the Shockwave Flash plugin, try toggling it. Here's what I mean:

(1) Open the Add-ons page to the Plugins section

• Ctrl+Shift+a > Plugins
• orange Firefox button (or Tools menu) > Add-ons > Plugins

(2) Change the setting for Shockwave Flash to "Never Activate" and pause while Firefox updates the setting

(3) Change the setting for Shockwave Flash to "Always Activate" and pause while Firefox updates the setting

Does that make any difference?

Ah!!!!! Now we come to a better understanding about why 25 may cause some systems to "break". Something that "Firefox" knew that it was, or could do to its settings. Something that users were not aware of beforehand. Do we all have to go somewhere and read all about the various changes that are going to happen when these updates happen??? And how many are even if we know we are supposed to. And some will have their systems to go ahead and automatically update their system as soon as the update becomes available - whether they go look to see what the changes are or not. Might it not be better to do something similar to Windows updates? Include information about the update along with the update itself. What I did is go through and disabled SEVERAL of my addons and for whatever reason YouTube worked. Since Firefox did not tell me any of these are no longer compatible with Firefox, I have to go through the process of seeing which one MIGHT have "broke" it. Now you tell me about this "toggling" of settings, and maybe that is the problem to begin with. I reviewed all these settings, and it is "always activate", but no, I did not toggle it. I didn't know I needed to, or might need to. Obviously, it is something that was known about. Why didn't you let me know beforehand. I have not yet started working towards re-enabling my extensions yet, so I can't tell you if that was it or not. It just happens I am presently working on a high school class reunion involving about 700 people, and getting to the bottom of this Firefox issue is not on the top of my list. Especially not when I can use IE, if necessary. Thanks for letting me know what the real issue may have been, though.

Hi rocmar62, the suggestion to toggle the Always Activate/Never Activate setting was just a guess, not a solution I've ever heard of before, in relation to plugins not working. On rare occasions, volunteers have seen cases where a dialog will say A but the truth is B, and switching the settings back and forth fixes the corrupted setting. The odds of a corrupted setting are low, but I suggested it in case everything else checked out and we were down to chasing gremlins.

When Firefox checks compatibility for extensions, it is checking for stated compatibility (i.e., the extension lists a range of compatible version and whether the upper bound should be strictly enforced). There are times that the author becomes aware, before or after release, that there is a functionality problem in a new version of Firefox. Firefox's compatibility check has no access to this information which may appear in reviews, or on a separate website. Mozilla sometimes issues a block on an add-on if it causes a lot of crashes, but otherwise, the problem is left to the add-on's author to solve.

While Microsoft's documentation is admirable, it definitely is not complete. Earlier this year, one of Microsoft's updates was found to ruin font rendering in many configurations of Firefox. I'm pretty sure that wasn't in the the Technet or MSKB documentation, and the fact that it routinely gets installed when IE9 users install IE10 further disguises the source of the problem.

But I digress... a great place to keep up with Firefox changes is this blog: http://www.ghacks.net/category/firefox/

Your statement: "I missed that Firefox 25 turned on "click to play" as the default behavior for plugins. I assume you prefer to have Flash run automatically if you've approved the site in NoScript." I didn't read anything anywhere, nor was I aware of the fact that Firefox may have changed "my" plugin settings, or broken them. How many users do you think there might be that have NoScript set this way for one or more sites. I'm just saying it might have been nice to have been forewarned about this - obviously something that was KNOWN that the update was going to do!!!!!!!!!!!!!!!

Hi rocmar62, I did say Firefox 25 turned on "click to play" as the default behavior for plugins. What wasn't clear from that statement was that the upgrade was designed to preserve your existing choice between Always Active and Never Activate for your presently installed plugins, while adding the third choice of Ask to Activate. I did not personally notice any of my plugins changing behavior from before the update to after, and I can't recall seeing any threads where that has come up as a problem. It seem the conversion went smoothly in most cases, but any conversion involves the possibility of corruption, i.e., results not matching intent, so I suggested a workaround for that possible scenario. Forget I mentioned it.

Thanks, I was having the same issue, and sure it enough. It was a extention blocking app that was messing up things. uninstalled it and works fine now. Thks :)