Note: A few contributors expressed interest in getting release notes earlier.
Unfortunately release notes tend to be written up the day before a release goes out. However, I've decided to start posting the beta release notes- since these will usually be 90% the same as the final release for that version.
==============
Firefox 40.0beta, is scheduled for release on July 1, 2015
It's important to remember that not all of the items listed in these release notes will make it into the final Firefox 40 release.
==========================
Note: A few contributors expressed interest in getting release notes earlier.
Unfortunately release notes tend to be written up the day before a release goes out. However, I've decided to start posting the beta release notes- since these will usually be 90% the same as the final release for that version.
==========================
Firefox 40.0beta, is scheduled for release on July 1, 2015
'''Draft Release Notes:'''
https://www-dev.allizom.org/en-US/firefox/40.0beta/releasenotes/ - Desktop
https://www-dev.allizom.org/en-US/firefox/android/40.0beta/releasenotes/ - Android
None of these updates look to major for users.
"Download protection from potentially unwanted software" refers to an update to the Google Safe Browsing API. More information here: http://googleonlinesecurity.blogspot.be/2015/03/even-more-unwanted-software-protection.html
''It's important to remember that not all of the items listed in these release notes will make it into the final Firefox 40 release.''
I suppose you are trying to get help with a Firefox problem.
Could I ask you to post in the dedicated support forum.
When doing so try to follow the prompts to include troubleshooting information.
Please use the link https://support.mozilla.org/en-US/que.../desktop
Thanks.
This is not the correct place to post support questions but if you post back here again to confirm you have posted a question we will be able to help you and make sure your new question is answered.
The Beta version is not the one that ordinary new user would be expected to use, but we can explain later how to get and install the correct version, without losing information.
''zzetina18.2 [[#post-65857|said]]''
<blockquote>
ok i need you.
</blockquote>
Hi zzetina,
Welcome to Mozilla Support
I suppose you are trying to get help with a Firefox problem.
Could I ask you to post in the dedicated support forum.
When doing so try to follow the prompts to include troubleshooting information.
'''Please use the link [https://support.mozilla.org/en-US/questions/new/desktop]'''
Thanks.
-------
This is not the correct place to post support questions but if you post back here again to confirm you have posted a question we will be able to help you and make sure your new question is answered.
The Beta version is not the one that ordinary new user would be expected to use, but we can explain later how to get and install the correct version, without losing information.
No link was provided but here's the related bug:
Bug 989469 - Use InContent prefs styling for add-on manager
According to this MozillaZine thread there's no easy way to revert to the old style Add-ons manager ... unless you can find an extension.
''Marko [[#post-65872|said]]''
<blockquote>
Is it possible to revert the Add-ons Manager back to the previous style? I don't like the new one.
</blockquote>
https://www.mozilla.org/en-US/firefox/40.0beta/releasenotes/
Quote:
'''New''' | New style for add-on manager based on the in-content preferences style
No link was provided but here's the related bug:
[https://bugzilla.mozilla.org/show_bug.cgi?id=989469 Bug 989469] - Use InContent prefs styling for add-on manager
According to [http://forums.mozillazine.org/viewtopic.php?f=23&t=2938793 this MozillaZine thread] there's no easy way to revert to the old style Add-ons manager ... unless you can find an extension.
my main issue with the new addon manager style is that it hides plugin version numbers atm which will make live miserable for us in support (especially in situations like now, when there are flash blocklists deployed and users shouldn't be left guessing which version they are on).
i've filed bug 1178425 about this and am not sure where it's going yet - please fell free to way in there...
my main issue with the new addon manager style is that it hides plugin version numbers atm which will make live miserable for us in support (especially in situations like now, when there are flash blocklists deployed and users shouldn't be left guessing which version they are on).
i've filed [https://bugzilla.mozilla.org/show_bug.cgi?id=1178425 bug 1178425] about this and am not sure where it's going yet - please fell free to way in there...
my main issue with the new addon manager style is that it hides plugin version numbers atm which will make live miserable for us in support (especially in situations like now, when there are flash blocklists deployed and users shouldn't be left guessing which version they are on).
Workaround: the version number is displayed in a tooltip when you hover the cursor above the plugin.
''AliceWyman [[#post-65874|said]]''
<blockquote>
According to [http://forums.mozillazine.org/viewtopic.php?f=23&t=2938793 this MozillaZine thread] there's no easy way to revert to the old style Add-ons manager ... unless you can find an extension.
</blockquote>
Too bad. I wonder why are they making such changes. Hopefully Classic Theme Restorer or another extension will enable us to get rid of it.
''philipp [[#post-65876|said]]''
<blockquote>
my main issue with the new addon manager style is that it hides plugin version numbers atm which will make live miserable for us in support (especially in situations like now, when there are flash blocklists deployed and users shouldn't be left guessing which version they are on).
</blockquote>
Workaround: the version number is displayed in a tooltip when you hover the cursor above the plugin.
I've read that Firefox will be officially available in 64-bit mode since v40. Will the x64 version automatically replace the x86 version on 64-bit OSes?
I've read that Firefox will be officially available in 64-bit mode since v40. Will the x64 version automatically replace the x86 version on 64-bit OSes?
for the moment, users will have to opt-in to the 64bit builds which will only be available at the download page for all languages & systems at: https://www.mozilla.org/firefox/all/
for the moment, users will have to opt-in to the 64bit builds which will only be available at the download page for all languages & systems at: https://www.mozilla.org/firefox/all/
I've read that Firefox will be officially available in 64-bit mode since v40. Will the x64 version automatically replace the x86 version on 64-bit OSes?
I think you will need to install the Win64 to replace the Win32 build on 64-bit Windows. If you have Win32 Firefox 39.0 you would get Win32 Firefox 40.0 in update.
There was talk of having a stub installer for Windows that would install the version based on what OS and hardware you have.
64-bit Firefox is not new in that it has been available for Mac OSX (combined 32/64) and Linux from mozilla.org since Firefox 4.0 both because it was needed and easier.
Note you will need 64-bit Windows 7 or newer Windows to use Win64 as they will not work on 64-bit WinXP, Vista and servers as you can still use 32-bit.
Bug 1093741
The 64-bit Firefox.exe itself will no longer run on older operating systems than Windows 7 since bug 1094013. BTW Firefox.exe itself has no checks. The operating system is the one that checks the subsystem version of the executable.
''Marko [[#post-66102|said]]''
<blockquote>
I've read that Firefox will be officially available in 64-bit mode since v40. Will the x64 version automatically replace the x86 version on 64-bit OSes?
</blockquote>
Yes Firefox 40.0 may be the first to have Win64 for Release. The Win64 will be served on www.mozilla.org/firefox/all and not www.mozilla.org initially.
I think you will need to install the Win64 to replace the Win32 build on 64-bit Windows. If you have Win32 Firefox 39.0 you would get Win32 Firefox 40.0 in update.
There was talk of having a stub installer for Windows that would install the version based on what OS and hardware you have.
64-bit Firefox is not new in that it has been available for Mac OSX (combined 32/64) and Linux from mozilla.org since Firefox 4.0 both because it was needed and easier.
Note you will need 64-bit Windows 7 or newer Windows to use Win64 as they will not work on 64-bit WinXP, Vista and servers as you can still use 32-bit.
Bug 1093741
<blockquote>The 64-bit Firefox.exe itself will no longer run on older operating systems than Windows 7 since bug 1094013. BTW Firefox.exe itself has no checks. The operating system is the one that checks the subsystem version of the executable.</blockquote>
Do we have a checklist of issues raised by migrating between 32-bit and 64-bit Firefox?
For example, I notice that my pluginreg.dat on 32-bit Firefox does not list plugins under the 64-bit keys in the Windows Registry. Presumably that would be reversed in 64-bit Windows. A handful of users who toggled off the plugin.scan.plid.all preference might be left with an invalid pluginreg.dat file.
Do we have a checklist of issues raised by migrating between 32-bit and 64-bit Firefox?
For example, I notice that my pluginreg.dat on 32-bit Firefox does not list plugins under the 64-bit keys in the Windows Registry. Presumably that would be reversed in 64-bit Windows. A handful of users who toggled off the '''plugin.scan.plid.all''' preference might be left with an invalid pluginreg.dat file.
The only 64-bit Plugin that will be used on Win64 Firefox 40.0 Release is the 64-bit Flash player plugin.
Bug 1165981 - Whitelist Flash for NPAPI on 64 bit Firefox on Win64
The only 64-bit Plugin that will be used on Win64 Firefox 40.0 Release is the 64-bit Flash player plugin.
Bug 1165981 - Whitelist Flash for NPAPI on 64 bit Firefox on Win64
Well it looks like there is not going to be Win64 for Firefox 40.0.
from Bug 1180792 comment 4
Javaun Moradi [:javaun] 2015-07-29
We've decided not to release win64 builds in Fx40. We will wait until 41, and the improvements launching there: sandboxing and NPAPI whitelisting, and possibly some other fixes. I've spoken to the relevant folks on platform and we're fine here. Our original plan was a quiet soft-launch in 40, and to make more noise in 41 when we have added safety. We'll launch in 41.
Well it looks like there is not going to be Win64 for Firefox 40.0.
from Bug 1180792 comment 4
<blockquote>Javaun Moradi [:javaun] 2015-07-29
We've decided not to release win64 builds in Fx40. We will wait until 41, and the improvements launching there: sandboxing and NPAPI whitelisting, and possibly some other fixes. I've spoken to the relevant folks on platform and we're fine here. Our original plan was a quiet soft-launch in 40, and to make more noise in 41 when we have added safety. We'll launch in 41.</blockquote>
Starting in Firefox 40, the included set of search engine plugins are now part of the omni.ja file, which contains internal pages, scripts, etc. This was an anti-hijacking measure.
Starting in Firefox 40, the included set of search engine plugins are now part of the omni.ja file, which contains internal pages, scripts, etc. This was an anti-hijacking measure.
See: [https://bugzilla.mozilla.org/show_bug.cgi?id=1162569 Bug 1162569 – default engine files should be in the omni.ja file].
Some users who modified the .xml files in the program folder may be disoriented. I would suggest adding modified search plugins to the profile folder.
It may also be necessary to rename the file and the ShortName inside the file (max 16 characters).
Suggested all this to a beta user and haven't heard back yet in this thread: https://support.mozilla.org/questions/1075655
Help Test Firefox Beta on Windows 10
We wanted to make sure that Firefox showed up on Windows 10 as a first-class experience, so we’ve made a lot of subtle tweaks to the look and feel that both sit well in the Windows 10 context and are definitively Firefox. We’re taking visual cues from style changes appearing in Windows 10 and we’re also reducing the overall browser UI footprint to increase space for viewing the Web. Download Firefox Beta now to help test out these updates or watch out for them coming soon in the general release of Firefox!
Of course we don't really support users using multiple profiles. Or explain any of the downsides of becoming a beta tester.
Are we now going to have to be prepared to fully support users on the beta channel.
We now have a prominent blog
* '''''Firefox for Windows 10: How to Restore or Choose Firefox as Your Default Browser''''' https://blog.mozilla.org/futurereleases/2015/07/29/firefox-for-windows-10-how-to-restore-or-choose-firefox-as-your-default-browser/
<blockquote>Help Test Firefox Beta on Windows 10
We wanted to make sure that Firefox showed up on Windows 10 as a first-class experience, so we’ve made a lot of subtle tweaks to the look and feel that both sit well in the Windows 10 context and are definitively Firefox. We’re taking visual cues from style changes appearing in Windows 10 and we’re also reducing the overall browser UI footprint to increase space for viewing the Web. Download Firefox Beta now to help test out these updates or watch out for them coming soon in the general release of Firefox!</blockquote>
Of course we don't really support users using multiple profiles. Or explain any of the downsides of becoming a beta tester.
I will cross post this into the KB forum.
-----
Now posted as
* ''Do we need to ramp up Firefox Beta support, for users testing Windows 10'' [/forums/knowledge-base-articles/711457]
Two Firefox 40 users report the HP Simplepass plugin is not working:
* https://support.mozilla.org/questions/1077181 - Windows 7
* https://support.mozilla.org/questions/1077183 - Windows 10
Not sure what to suggest except to contact HP. ??
40.0.1 is coming due to a Windows 10 bug setting Firefox as the default browser. See [https://bugzilla.mozilla.org/show_bug.cgi?id=1172724#c22 bug 1172724 comment 22] and [https://bugzilla.mozilla.org/show_bug.cgi?id=1179249#c14 bug 1179249 comment 14]. Details in [https://bugzilla.mozilla.org/show_bug.cgi?id=1193196 bug 1193196].
there's a widely reported startup crash reported by users on osx with trusteer rapport after auto-updating to firefox 40:
https://bugzilla.mozilla.org/show_bug.cgi?id=1194169
https://support.mozilla.org/en-US/questions/firefox?owner=all&tagged=bug1194169&show=all
