…starting with Firefox 42 but you need to go to the Mozilla FTP site in order to download it. Once you click the link, find the most current version of Firefox and click that link, then click on the win64 link. Choose your localized (language) build then download the .exe setup file. At sometime in the future, the Win64 build will be offered directly from the Firefox downloads page.
Per Bug 1181014, 32-bit Windows users who are running 64-Bit version of Windows will be offered an updated to the 64-bit version. This likely won’t happen until sometime next year after some more testing is done to insure this won’t create new problems.
At least for a while as Mozilla still plans on deprecating Silverlight support sometime in the future (much as Google and Microsoft already have). Bug 1225293 which was made public today indicates Mozilla’s short term plans to support Silverlight in the Win64 builds. When exactly Silverlight will return to the Firefox 64-Bit builds is not exactly known. It could (but not likely) be with Firefox 43 already in Beta and due out December 15th, 2015 or (more likely) Firefox 44 still in Developer’s Edition (Aurora) and due out in late January 2016 or Firefox 45 currently in Nightly builds and due out early March 2016.
Besides Netflix and Amazon, there are many other small regional VOD services which utilize Silverlight. So going forward both Flash and Silverlight (for a while) will be supported in the Win64 releases of Firefox. We will post an updated when we get more info as to which release of Firefox this will land.
Seems longer. I have an old laptop with a working version of 1.something.
"Eleven years ago, Firefox 1.0 was released with much excitement and anticipation. With the help of volunteers, The Mozilla Foundation placed a two-page advertisement in the New York Times. Over the last 11 years, Firefox has been been used by millions of people worldwide, becoming one of the most popular web browsers available to surf the Internet. ..."
Source: Opensource-com Happy birthday Firefox!
Mozilla release the next scheduled update of Firefox with Firefox 42 on Tuesday, November 3rd. There are several changes and updates to this version including changes to private browsing. More information is available in the Release Notes
. Depending on their update settings, users should be prompted to update within 48-hours of this release or can do so in Firefox via Help > About Firefox or download and manually install the new version via the getfirefox.com
The next scheduled release is Firefox 43 set for around December 15th.
The title of this post sounds quite like a marketing gimmick by Microsoft to promote their new Windows 10 browser. It could be for a TV commercial or online advertisement. Actually it is the messages Windows 10 users may
see if a new 'feature' in a forthcoming Windows 10 update is left in place when they attempt to change their default browser to Google Chrome or Mozilla Firefox.
Microsoft has already made it a pain for users
to change their default browser
by making them do it from within the Windows 10 settings instead of allowing from within the browser itself. But, now they are begging you not to change your default browser. Again, this change is in a yet to be released update for Windows 10 and it could be yanked (though not likely unless say the EU gets on Microsoft's case again) before released to the public.
via Forbes > Gordon Kelly
On Thursday, October 15th, Mozilla released an update for the Firefox 41.0 branch with Firefox 41.0.2. This update addressed the following issues:
The next planned release will be Firefox 42 on November 3rd.
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 not to mention insecure. The problem is some content providers such as Netflix still use Silverlight for users of Firefox while providing users of Google Chrome and Microsoft Edge the modern HTML5 version of their services. It is hopeful this announcement from Mozilla will be the kick in the pants these content providers need to start doing away with Silverlight.
Mozilla intends to remove support for most NPAPI plugins in Firefox by the end of 2016. Firefox began this process several years ago with manual plugin activation, allowing users to activate plugins only when they were necessary. This decision mirrors actions by other modern browsers, such as Google Chrome and Microsoft Edge, which have already removed support for legacy plugins. Moreover, since new Firefox platforms do not have to support an existing ecosystem of users and plugins, new platforms such as 64-bit Firefox for Windows will launch without plugin support.
via Mozilla Future Releases
Windows only at the moment - I'm not on Windows so can't try it out but it looked like something that may be useful for some.
Source: The Windows Club
Review ConfigFox: Configure and tweak Firefox about:config settings
Source: gHacks Tech News
Review ConfigFox: manage advanced Firefox privacy and security settings