“… Mozilla and the Web as a whole have been taking steps to reduce the need for Flash content in everyday browsing. Starting in August, Firefox will block certain Flash content that is not essential to the user experience, while continuing to support legacy Flash content. These and future changes will bring Firefox users enhanced security, improved battery life, faster page load, and better browser responsiveness. …” Source: Mozilla Reducing Adobe Flash Usage in Firefox | Future Releases
Adobe Flash
Read More
Following in the footsteps of Google and Microsoft, Mozilla plans to eliminate support for the ancient NPAPI plugins (with the exception of heavily sandboxed version of Flash) in the next year. This would include the 32-bit versions of Firefox. There has been a lot of heated discussions in the past few months in regards to Mozilla removing the support of NPAPI plugins (mainly Silverlight and Java) from the upcoming (Firefox 43?) Windows 64-bit (Win64) version of Firefox. I agree this needs to be done as NPAPI plugin technology is over 20-years old from the Netscape days and is badly outdated…
People are still complaining about how Mozilla is removing support for NPAPI plugins (Silverlight and Java specifically) in the upcoming Windows 64-Bit release of Firefox (now tentatively scheduled for Firefox 42 in November) even though the move is not that unusual given the trend to move away from NPAPI plugins by other browsers. Microsoft’s Edge Browser (Windows 10 only) does not support Active X or any of the NPAPI plugins (Flash is integrated not a plugin). On Tuesday, September 1st Google released Chrome 45 which ended the browser’s support of NPAPI plugins as well. I found this out when I…
I don’t know anything about this distro but the use of Pepper Flash with Firefox is interesting.I’m wondering if the other “flavors” will do this. Notable changes: Nemo updated to 2.6.7 Running kernel 3.13.0-63 Firefox 40.0.3 Fixed Grub installing issues. Fixed Docky & Network issues after waking from suspend. Using Pepper Flash in Firefox instead of Adobe Flash. Added the H.265/HEVC Codec for VLC. Source: Pinguy OS
The plans to ‘officially’ release a Win64 release of Firefox have now been pushed back to Firefox 42 (November 2015). As you may recall it was suppose to be Firefox 40 (August 2015) then was pushed to Firefox 41 (September 2015). The reason for the delay as described in Bug 1185532 has to do with the sandboxing feature for the 64-Bit Flash not working correctly.
I understand what Mozilla is doing with in the Win64 Firefox in regards to only allowing the Flash NPAPI plugin. It starts to make sense if you look at the browser ‘market’ as a whole. Microsoft’s new Edge browser (Windows 10) does not support SilverLight and Java and neither does/will Chrome (Google plans to phase out NPAPI plugins by end of 2015). All of these browsers including the Win64 Firefox do support Flash. Also, remember Flash is integrated (no plugin) into Chrome as Google bribed paid Adobe to build a custom version of Flash directly into Chrome. It is almost painful…
So, still no official (or even unofficial) explanation from Mozilla as to why they suddenly (as in July 9th) banished Silverlight NPAPI from the upcoming Win64 Firefox releases. Mozilla’s silence on this dramatic change with the Win64 Fx is a bad thing for things to come. Why are they being so secretive? Why choose the worse of two evils (Flash)? Why continue to support a plugin that everyone (including Facebook) is trying to move away from (Flash > HTML5)? So yesterday the discussion in Bug 1165981 (this was the bug that was suppose to Whitelist BOTH Flash and Silverlight NPAPI in…
In a very odd move Mozilla has made a change to the latest Firefox Nightly (Firefox 42) Win64 which only allows the Shockwave Flash NPAPI plugin. Note: the Prime Content Decryption and Open H264 are now standard all will always be supported. While Shockwave Flash is still supported Silverlight is not. Simple enough, just install the plugin and you’re ready to go. Users won’t be able to install Silverlight in the Win64 version of Firefox since it is not allowed. Microsoft’s Silverlight is used by Netflix and Amazon Video along with many other Video on Demand (VOD) sites (especially outside the US). This is a result…
With all the talk recently about the exploits in Flash and Java, users are taking a closer look at their Firefox plugins. A couple plugins users may come across that look a little odd are the ones which provide HTML5 support in Firefox. Now remember, HTML5 Video is suppose to someday replace Adobe’s Flash (for the most part YouTube has been using HTML5 since early this year) and Microsoft’s Silverlight (no longer supported, but still used). These plugins are: Open H.264 Video Codec provided by Cisco Systems - shipped starting with Firefox 33 and allows playing of H.264 encoded content natively via…
On Monday (July 13th), Trend Micro reported the now third bug (CVE-2015-5123) to Adobe’s Security Team. This comes just as Adobe was getting ready to push out the update 18.0.0.209 which had addressed two Zero Day vulnerabilities discovered with verison 18.0.0.203 earlier. No word yet when Adobe is going to push out a patch for this vulnerability. via: Krebs on Security