So, currently, the plan is standing to ship Firefox 11 tomorrow. The goal is to have it out as early as possible but not at our usual time of 8 AM (horray!)
As for top issues that we know of, there aren't any particularly new ones that weren't fixed:
The top issues according to input are complaints about slowness (especially with loading pages) and complaints about plugin support.
The main concerns are actually around the way this release is going out with the numerous rebuilds:
Because we were making changes at the last minute, there are some concerns that firewalls/antivirus may not be updated in time so early adopters are more likely to have connectivity problems. Also add-ons that wait until final builds are likely to be delayed.
Also, tomorrow is Microsoft Patch Tuesday. From what we know, this shouldn't be a problem but it did cause us problems with earlier releases. Because of this, the release will be manual-only and we'll checkpoint on Thursday to discuss a full release. (*)
Please update this thread if you discover new issues throughout the day.
(*) Note: users who are on Firefox 11 and have problems with the Microsoft Patch Tuesday and use system restore to go back aren't going to get future automatic updates and will need to do a clean install. See bug: 730285. (This was actually a bug on 10 but we're likely to see it this time because Patch Tuesday coincides with release day).
UPDATE:
Some early returns from input.m.o (I'll be filing/looking for bugs for these tomorrow morning pending QA but it's late here):
Microsoft security essentials hangs Firefox when downloading (probably during virus scan/initialization). Update: seems to be reduced in number now, maybe they fixed something
Confusion because the new way images are displayed on their own is centered-on-dark grey instead of left-aligned on white. We should document this
Norton and AVG aren't compatible yet. Update: both should be compatible now, users have to update via the AV update process and may have to reinstall Firefox afterwards
Firefox is really slow to load pages after update. (Almost feels like firewall is throttling this version of Firefox... didn't ZoneAlarm do something like this in the past?)
Pages load "smushed to the left"... possibly missing or broken CSS, if you see a user with this problem, can you ask them to take a screenshot and then try shift-reloading?
Lots of complaints about facebook apps not loading/not being able to log in but that may just be normal traffic.
Update 2
Here are some more top issues after a weekend of untrottling:
More than the usual number of people seem to be losing bookmarks/passwords/history/sessions on update. Not sure what's going on. There are a couple comments that suggest a profile is getting messed up.
nVidia wants us to document that 3D (stereoscopic) videos don't work (even though they should with their 3D graphics cards). This is a regression: bug 725152
We're trying to debug a situation where some users are getting the "Welcome to Firefox" screen even though it should be turned off for this update. Please post here if you see cases of this and help us try to figure out why.
Some users are reporting problems with opening new tabs (some people say that it's opening windows instead, some are saying it's making a new tab when they don't want it). This is caused by an extension but I don't know which one.
Update 3
If you select text on a "complex" page (selection in a table, or maybe even across divs) and print selection, you get a blank page. This is bug 736915.
So, currently, the plan is standing to ship Firefox 11 tomorrow. The goal is to have it out as early as possible but not at our usual time of 8 AM (horray!)
As for top issues that we know of, there aren't any particularly new ones that weren't fixed:
The top issues according to input are complaints about slowness (especially with loading pages) and complaints about plugin support.
The main concerns are actually around the way this release is going out with the numerous rebuilds:
Because we were making changes at the last minute, there are some concerns that firewalls/antivirus may not be updated in time so early adopters are more likely to have connectivity problems. Also add-ons that wait until final builds are likely to be delayed.
Also, tomorrow is Microsoft Patch Tuesday. From what we know, this shouldn't be a problem but it did cause us problems with earlier releases. Because of this, the release will be manual-only and we'll checkpoint on Thursday to discuss a full release. (*)
Please update this thread if you discover new issues throughout the day.
(*) Note: users who are on Firefox 11 and have problems with the Microsoft Patch Tuesday and use system restore to go back aren't going to get future automatic updates and will need to do a clean install. See bug: [https://bugzilla.mozilla.org/show_bug.cgi?id=730285 730285]. (This was actually a bug on 10 but we're likely to see it this time because Patch Tuesday coincides with release day).
== UPDATE: ==
Some early returns from input.m.o (I'll be filing/looking for bugs for these tomorrow morning pending QA but it's late here):
# Microsoft security essentials hangs Firefox when downloading (probably during virus scan/initialization). '''Update: seems to be reduced in number now, maybe they fixed something'''
# Confusion because the new way images are displayed on their own is centered-on-dark grey instead of left-aligned on white. '''We should document this'''
# Norton and AVG aren't compatible yet. '''Update: both should be compatible now, users have to update via the AV update process and may have to reinstall Firefox afterwards'''
# Firefox is really slow to load pages after update. (Almost feels like firewall is throttling this version of Firefox... didn't ZoneAlarm do something like this in the past?)
# Pages load "smushed to the left"... possibly missing or broken CSS, if you see a user with this problem, can you ask them to take a screenshot and then try shift-reloading?
# Lots of complaints about facebook apps not loading/not being able to log in but that may just be normal traffic.
===Update 2===
Here are some more top issues after a weekend of untrottling:
# More than the usual number of people seem to be losing bookmarks/passwords/history/sessions on update. Not sure what's going on. There are a couple comments that suggest a profile is getting messed up.
# nVidia wants us to document that 3D (stereoscopic) videos don't work (even though they should with their 3D graphics cards). This is a regression: bug 725152
# We're trying to debug a situation where some users are getting the "Welcome to Firefox" screen even though it should be turned off for this update. Please post here if you see cases of this and help us try to figure out why.
# Some users are reporting problems with opening new tabs (some people say that it's opening windows instead, some are saying it's making a new tab when they don't want it). This is caused by an extension but I don't know which one.
===Update 3===
# If you select text on a "complex" page (selection in a table, or maybe even across divs) and print selection, you get a blank page. This is bug 736915.
(*) Note: users who are on Firefox 11 and have problems with the Microsoft Patch Tuesday and use system restore to go back aren't going to get future automatic updates and will need to do a clean install. See bug: 730285. (This was actually a bug on 10 but we're likely to see it this time because Patch Tuesday coincides with release day).
Do they have to do a clean install or just a regular install? Last time, we had them do a clean install until 9.0.1(?) was released and then they could just do a regular install.
''Cww [[#post-45745|said]]''
<blockquote>
(*) Note: users who are on Firefox 11 and have problems with the Microsoft Patch Tuesday and use system restore to go back aren't going to get future automatic updates and will need to do a clean install. See bug: [https://bugzilla.mozilla.org/show_bug.cgi?id=730285 730285]. (This was actually a bug on 10 but we're likely to see it this time because Patch Tuesday coincides with release day).
</blockquote>
Do they have to do a clean install or just a regular install? Last time, we had them do a clean install until 9.0.1(?) was released and then they could just do a regular install.
Firefox desktop 3.6.28 (This will be the last planned release for 3.6, users should migrate to ESR over the next 6 weeks -- there will still be chemspill support, though.)
On top of this, there is a Thunderbird release, and a Seamonkey release.
Just a note:
The Firefox versions that are going out are:
* Firefox desktop 11
* Firefox desktop 10.0.3 ESR
* Firefox mobile 10.0.3
* Firefox desktop 3.6.28 (This will be the last planned release for 3.6, users should migrate to ESR over the next 6 weeks -- there will still be chemspill support, though.)
On top of this, there is a Thunderbird release, and a Seamonkey release.
FWIW, because we haven't fully released, Firefox 11 is still going to be tagged beta in SUMO and http://www.mozilla.org/en-US/firefox/11.0/whatsnew/ is showing "you're out of date". This should be fixed as soon as we've released properly.
FWIW, because we haven't fully released, Firefox 11 is still going to be tagged beta in SUMO and http://www.mozilla.org/en-US/firefox/11.0/whatsnew/ is showing "you're out of date". This should be fixed as soon as we've released properly.
''Cww [[#post-45745|said]]''
<blockquote>
'''UPDATE:'''
<br><br>
Some early returns from input.m.o (I'll be filing/looking for bugs for these tomorrow morning pending QA but it's late here):
# Microsoft security essentials hangs Firefox when downloading (probably during virus scan/initialization).
<snip>
</blockquote>
I found [https://bugzilla.mozilla.org/show_bug.cgi?id=551427 bug 551427] that seems related but it's not specific to Microsoft Security Essentials or Firefox 11.
P.S. Setting '''browser.download.manager.scanWhenDone''' to "false" in about:config is a possible workaround which is already suggested in [[Firefox crashes when trying to download a file]] and which probably belongs in the [[Firefox hangs]] article. Ref:
http://kb.mozillazine.org/Firefox_hangs#Hang_downloading_files under "Virus scanning".
Old default image style should revert the behavior of grey backgrounds on standalone images.
[https://addons.mozilla.org/en-US/firefox/addon/old-default-image-style/ Old default image style] should revert the behavior of grey backgrounds on standalone images.
It tells me that FF is out of date and suggests upgrade to v11. As the purpose of the ESR is so companies can stick with one version, I would ask/suggest that the splash page for ESR installs be modified to detect if you are on the latest ESR install or not. Then maybe in tiny text say that the mainline version of FF is available at <link here>
It seems that with Firefox 11 s release Firefox ESR 10.0.3 is giving a splash screen advising update to Firefox 11 !!
This was reported in a support forum question, maybe someone would like to comment on this and possibly file a bug to correct it.
See [/questions/923043] from [https://support.mozilla.org/en-US/user/680164 halsteaw]
<blockquote>Home Page after ESR install suggesting update to Mainline install.<br/><br/>
The splash pages after the ESR install of 10.0.3 is http://www.mozilla.org/en-US/firefox/10.0.3/whatsnew/ <br/><br/>
It tells me that FF is out of date and suggests upgrade to v11. As the purpose of the ESR is so companies can stick with one version, I would ask/suggest that the splash page for ESR installs be modified to detect if you are on the latest ESR install or not. Then maybe in tiny text say that the mainline version of FF is available at <link here> </blockquote>
Some users complain that they lost some favicons of their bookmarks after the upgrade. It's likely caused by the fix of bug 699793 and the fact that the browsing history has an expiration duration (90 days?).
Some users complain that they lost some favicons of their bookmarks after the upgrade. It's likely caused by the fix of [https://bugzilla.mozilla.org/show_bug.cgi?id=699793 bug 699793] and the fact that the browsing history has an expiration duration (90 days?).
'''Edit: [https://addons.mozilla.org/firefox/addon/checkplaces/ CheckPlaces] fixes that issue.'''
Some users are reporting problems with opening new tabs (some people say that it's opening windows instead, some are saying it's making a new tab when they don't want it). This is caused by an extension but I don't know which one.
It was caused by Tab Utilities that has been fixed since that.
''Cww [[#post-45745|said]]''
<blockquote>
Some users are reporting problems with opening new tabs (some people say that it's opening windows instead, some are saying it's making a new tab when they don't want it). This is caused by an extension but I don't know which one.
</blockquote>
It was caused by Tab Utilities that has been fixed since that.
nVidia wants us to document that 3D (stereoscopic) videos don't work (even though they should with their 3D graphics cards). This is a regression: bug 725152
I see there's a new article that was approved on March 20. I discovered it by accident, since scoobidiver has a revision pending review:
Have any other articles been created for new Firefox 11 issues? I don't see this one linked from Latest Firefox issues or anywhere else (Michael Verdi posted in the "Breaking issues team" thread that This team would quickly create a number of articles that we link in the various topic pages we have on the front page (this is instead of creating just one "latest issues" article).
''Cww [[#post-45745|said]]''
<blockquote>
nVidia wants us to document that 3D (stereoscopic) videos don't work (even though they should with their 3D graphics cards). This is a regression: bug 725152</blockquote>
I see there's a new article that was approved on March 20. I discovered it by accident, since scoobidiver has a revision pending review:
*[[3D videos do not work with certain NVIDIA drivers in Firefox 11]]
Have any other articles been created for new Firefox 11 issues? I don't see this one linked from [[Latest Firefox issues]] or anywhere else (Michael Verdi posted in the [/forums/contributors/708220 "Breaking issues team" thread] that ''This team would quickly create a number of articles that we link in the various topic pages we have on the front page (this is instead of creating just one "latest issues" article).''
