SUMO community discussions

Firefox 10, top issues, ESR and you!

  1. Update:

    Firefox 10.0.1 looks set to ship Friday 2/11 (probably in the afternoon). There will be no throttling of the release and it will also be when we untrottle updates from Firefox 9.0 to Firefox 10.0.1 (those users will skip 10.0, of course).

    Original post

    Firefox 10 ships tomorrow! We're trying out a new release strategy which should allow us to get traction quickly and allow a brief bit of evaluation time to see if a chemspill or emergency release is needed.

    Here's the current release plan:

    For manual updates (that is if you go to Help > About) starting at 8 AM PST, Firefox 10 will be available. It will also be available at mozilla.org/firefox for everyone. This means that if anyone asks about updates, just tell them that they can go to Help>About (Firefox>About Firefox on mac).

    For the first 24 hours (from 8 AM PST 1/31 to 8 AM PST 2/1) will be doing a partial release and not everyone will be updated.

    For the next few days we'll be evaluating the feedback. This is when we'll need your help. There is a SUMO day on Thursday when the focus will be on helping these Firefox 10 users. We really really want to hear about anything that could be a top issues/regression/breakage. Please post in this thread.

    Sometime Friday/Monday if everything looks good, we'll be unthrottling 100% and the release goes out to everyone.

    ESR

    You may have heard of ESR, which is "Extended Support Release". This is the version of Firefox we're going to be offering to Enterprise (and possibly university) users who need more than 6 weeks to qualify and deploy Firefox. Firefox 10 will be the first ESR release. You need to download a special ESR build to get it so there probably won't be many questions.

    If you get asked about this from personal users, tell them it's specifically for enterprise and deployment situations (and if they need help to talk to their IT department.) If you get questions about support or issues from IT professionals, tell them to sign up for and post questions to the Enterprise working group: https://wiki.mozilla.org/Enterprise#How_to_Participate_and_Post

    Top issues

    The following issues are KNOWN. However, it's very unclear how widespread they are/are going to be. Please help by linking to forum questions with these issues in this thread so that we can evaluate if they're worth a stop-ship for.

    1. The forward button is now conditional. That is, if there is nothing to go forward to, it will be hidden. (Only if you use big buttons). This may cause some confusion with users.
    2. Silverlight 5 (Netflix) may not work with some graphics cards on Macs
    3. The two-digit user agent may confuse some websites and users may get notifications that their browser is out-of-date. Please get URLs and we'll try to work with the sites to correct this.
    4. Extensions are now compatible by default... that means extensions that were compatible with Firefox 4 may suddenly come back and start sort-of working again. This does not affect binary extensions (so all antivirus extensions, most toolbars and most of the common things that break.)
    5. OSX 10.5 users (possibly with specific older graphics drivers) will crash with the Flip4Mac plugin (which plays WMV files/streams) and with an unofficial (but popular) hack of Flash (to support 10.5).

    The following issues really need users to help reproduce and figure out test cases (getting information like about:support info and what sites they're on)

    1. There may be a performance issue on Macs causing intermittent hangs (that gets progressively worse over time). Update: This looks to be a non-issue.
    2. There may be an issue where the caret (the bar that marks where you're typing, also called the cursor) disappears so you can't tell where you're typing. This may have something to do with having plugins open (possibly in a background tab). Update: There's a chance that this is related to bug 718939 which is fixed in the chemspill. Unfortunately we don't have steps to repro to prove this though. Other symptoms may include text areas not getting focus and being unable to highlight or select text.
    3. There may be a Windows startup crash that is the result of malware. (We don't know more, the number of users seems to have died back down but it's unclear why there was a new signature.) Update: This is more than just malware, but still unexplained.
    4. New: Some out of date versions of AVG Safe Search make pressing Enter in the location bar stop working. We are working on getting a full range of versions to blocklist. Users should disable the add-on or try updating AVG.
    5. New: Norton extensions don't work. Norton assures us that the updates exist. See this Symantec support article. However we're still getting complaints. Users may need to update Norton and then followup by re-enabling it from the add-ons manager. (Please let us know if that works.)
    6. New: Real Player Video Download doesn't work. This happens with pretty much every release, as Real Networks doesn't keep up with the release schedule.
    7. New: HTTPs does not work on some sites, often returning a connection reset. Firefox added a security measure (also in Chrome) which breaks HTTPs on some sites. Cor-el and I discuss it in depth in this forum thread which is probably a good place to point users.


    EDIT: See /forums/contributors/708145#post-45089 There will be a Firefox 10.0.1

    Cww said (posted February 7, 2012)

    After considering the top issues, the release drivers have decided to ship a Firefox 10.0.1 to fix two issues:

    1) A top startup crash (bug is security locked because it's a crash)

    2) Java applets cause text areas to hang (bug 718939)

    The issue with the add-ons manager is unclear at the moment but looks fixable with a hotfix so it doesn't warrant a chemspill. I'm looking to see if we can blocklist the versions of AVG Safe Search that are causing the broken location bar behavior.

    All other issues need too much investigation to be actionable right now or were deemed not to be major enough and can wait until Firefox 11.
    '''Update:''' Firefox 10.0.1 looks set to ship Friday 2/11 (probably in the afternoon). There will be no throttling of the release and it will also be when we untrottle updates from Firefox 9.0 to Firefox 10.0.1 (those users will skip 10.0, of course). '''Original post''' Firefox 10 ships tomorrow! We're trying out a new release strategy which should allow us to get traction quickly and allow a brief bit of evaluation time to see if a chemspill or emergency release is needed. Here's the current release plan: For manual updates (that is if you go to Help > About) starting at 8 AM PST, Firefox 10 will be available. It will also be available at mozilla.org/firefox for everyone. This means that if anyone asks about updates, just tell them that they can go to Help>About (Firefox>About Firefox on mac). '''For the first 24 hours''' (from 8 AM PST 1/31 to 8 AM PST 2/1) will be doing a partial release and not everyone will be updated. '''For the next few days''' we'll be evaluating the feedback. This is when we'll need your help. There is a SUMO day on Thursday when the focus will be on helping these Firefox 10 users. We really really want to hear about anything that could be a top issues/regression/breakage. Please post in this thread. Sometime Friday/Monday if everything looks good, we'll be unthrottling 100% and the release goes out to everyone. '''ESR''' You may have heard of ESR, which is "Extended Support Release". This is the version of Firefox we're going to be offering to Enterprise (and possibly university) users who need more than 6 weeks to qualify and deploy Firefox. Firefox 10 will be the first ESR release. You need to download a special ESR build to get it so there probably won't be many questions. If you get asked about this from personal users, tell them it's specifically for enterprise and deployment situations (and if they need help to talk to their IT department.) If you get questions about support or issues from '''IT professionals''', tell them to sign up for and post questions to the Enterprise working group: https://wiki.mozilla.org/Enterprise#How_to_Participate_and_Post '''Top issues''' The following issues are KNOWN. However, it's very unclear how widespread they are/are going to be. Please help by linking to forum questions with these issues in this thread so that we can evaluate if they're worth a stop-ship for. # The forward button is now conditional. That is, if there is nothing to go forward to, it will be hidden. (Only if you use big buttons). This may cause some confusion with users. # Silverlight 5 (Netflix) may not work with some graphics cards on Macs # The two-digit user agent may confuse some websites and users may get notifications that their browser is out-of-date. Please get URLs and we'll try to work with the sites to correct this. # Extensions are now compatible by default... that means extensions that were compatible with Firefox 4 may suddenly come back and start sort-of working again. This does not affect binary extensions (so all antivirus extensions, most toolbars and most of the common things that break.) # OSX 10.5 users (possibly with specific older graphics drivers) will crash with the Flip4Mac plugin (which plays WMV files/streams) and with an unofficial (but popular) hack of Flash (to support 10.5). The following issues really need users to help reproduce and figure out test cases (getting information like about:support info and what sites they're on) # There may be a performance issue on Macs causing intermittent hangs (that gets progressively worse over time). '''Update:''' This looks to be a non-issue. # There may be an issue where the caret (the bar that marks where you're typing, also called the cursor) disappears so you can't tell where you're typing. This may have something to do with having plugins open (possibly in a background tab). '''Update:''' There's a chance that this is related to bug 718939 which is fixed in the chemspill. Unfortunately we don't have steps to repro to prove this though. Other symptoms may include text areas not getting focus and being unable to highlight or select text. # There may be a Windows startup crash that is the result of malware. (We don't know more, the number of users seems to have died back down but it's unclear why there was a new signature.) '''Update:''' This is more than just malware, but still unexplained. # '''New:''' Some out of date versions of AVG Safe Search make pressing Enter in the location bar stop working. We are working on getting a full range of versions to blocklist. Users should disable the add-on or try updating AVG. # '''New:''' Norton extensions don't work. Norton assures us that the updates exist. See [http://community.norton.com/t5/Norton-Internet-Security-Norton/Firefox-10-Support-for-Norton-Toolbar/td-p/648241 this Symantec support article]. However we're still getting complaints. Users may need to update Norton and then followup by re-enabling it from the add-ons manager. (Please let us know if that works.) # '''New:''' Real Player Video Download doesn't work. This happens with pretty much every release, as Real Networks doesn't keep up with the release schedule. # '''New:''' HTTPs does not work on some sites, often returning a connection reset. Firefox added a security measure (also in Chrome) which breaks HTTPs on some sites. Cor-el and I discuss it in depth in [/questions/918127 this forum thread] which is probably a good place to point users. '''EDIT:''' See [/forums/contributors/708145#post-45089] There will be a Firefox 10.0.1 ''Cww said (posted February 7, 2012)'' <blockquote> After considering the top issues, the release drivers have decided to ship a Firefox 10.0.1 to fix two issues: <br><br> 1) A top startup crash (bug is security locked because it's a crash) <br><br> 2) Java applets cause text areas to hang (bug 718939) <br> <br> The issue with the add-ons manager is unclear at the moment but looks fixable with a hotfix so it doesn't warrant a chemspill. I'm looking to see if we can blocklist the versions of AVG Safe Search that are causing the broken location bar behavior. <br> <br> All other issues need too much investigation to be actionable right now or were deemed not to be major enough and can wait until Firefox 11. </blockquote>

    Modified by Cheng Wang on

  2. I may already have seen one of those:

    • [/questions/907443?] I have downloaded to new version of Firefox, but when I log into the internet, it tells me that I am not in the new version. What is the problem?
    I may already have seen one of those: *[[/questions/907443?]] I have downloaded to new version of Firefox, but when I log into the internet, it tells me that I am not in the new version. What is the problem?
  3. Cww, Could you include bug reports for the top issues? For example, for:
    2. Silverlight 5 (Netflix) may not work with some graphics cards on Macs
    ...I found this bug for 9.0.1 (Is there a new bug for Fx 10?):
    Bug 715396 - [Mac] Netflix not playing videos using 9.0.1 with some hardware
    ... it includes the following (workaround):


    Comment 47 Verdi 2012-01-19 09:27:01 PST

    From the support forum - user with Mac OS 10.6, Silverlight 5 and Firefox 9.0.1 - solved by running Fx in 32-bit mode https://support.mozilla.org/en-US/questions/913702

    '''Cww''', Could you include bug reports for the top issues? For example, for:<br> 2. Silverlight 5 (Netflix) may not work with some graphics cards on Macs<br> ...I found this bug for 9.0.1 (Is there a new bug for Fx 10?): <br> [https://bugzilla.mozilla.org/show_bug.cgi?id=715396 Bug 715396] - [Mac] Netflix not playing videos using 9.0.1 with some hardware<br> ... it includes the following (workaround): ----- ''Comment 47 Verdi 2012-01-19 09:27:01 PST'' ''From the support forum - user with Mac OS 10.6, Silverlight 5 and Firefox 9.0.1 - solved by running Fx in 32-bit mode https://support.mozilla.org/en-US/questions/913702''

    Modified by AliceWyman on

  4. The most irrirating/popular/top crash caused by Firebug has been fixed in Firefox 10 Firefox- Crash Report [@ js::AutoCompartment::AutoCompartment ]

    The most irrirating/popular/top crash caused by Firebug has been fixed in Firefox 10 Firefox- Crash Report [@ js::AutoCompartment::AutoCompartment ] * https://bugzilla.mozilla.org/show_bug.cgi?id=689118
  5. There are crashes for users with AMD Radeon HD 6xxx and HW acceleration turn on. HW acceleration will be turn off for these GPUs and version 8.92 and below via the block list. It's less likely that version 8.93 has a patch to fix that.

    Cww said

    There may be an issue where the caret (the bar that marks where you're typing, also called the cursor) disappears so you can't tell where you're typing. This may have something to do with having plugins open (possibly in a background tab).

    This issue happens to me regularly in Fx 9 so it's not a regression from Fx 10.

    There are [https://bugzilla.mozilla.org/show_bug.cgi?id=700288 crashes for users with AMD Radeon HD 6xxx and HW acceleration turn on]. HW acceleration will be [https://bugzilla.mozilla.org/show_bug.cgi?id=722538 turn off for these GPUs and version 8.92 and below via the block list]. It's less likely that version 8.93 has a patch to fix that. ''Cww [[#post-44879|said]]'' <blockquote> There may be an issue where the caret (the bar that marks where you're typing, also called the cursor) disappears so you can't tell where you're typing. This may have something to do with having plugins open (possibly in a background tab). </blockquote> This issue happens to me regularly in Fx 9 so it's not a regression from Fx 10.
  6. Bug 680927 - Startup crash in mozcomp.dll with Oracle Enterprise, F5 Networks, Passlogix V-GO, IBM Tivoli Access Manager SSO first appeared in Firefox 7 and is still a problem. According to comment 55, starting in Firefox 10 it causes a hang at startup rather than a crash.

    Ref: http://kb.mozillazine.org/Firefox_crashes#Crash_when_starting_Firefox

    Crashes at startup can occur in Firefox 7 or above (but not Firefox 6 or earlier) if you are using a corporate login system such as IBM Tivoli Access Manager or Oracle Enterprise Single Sign On Manager (bug 680927). See the bug report for a suggested workaround (details here), apply the fix from Oracle (see bug comments 58-61) or downgrade to Firefox 3.6.xx (available here) which is still being maintained. Note that, starting in Firefox 10, the same bug causes Firefox to hang at startup, rather than crash, with the process running in the background consuming CPU.
    [https://bugzilla.mozilla.org/show_bug.cgi?id=680927 Bug 680927 - Startup crash in mozcomp.dll with Oracle Enterprise, F5 Networks, Passlogix V-GO, IBM Tivoli Access Manager SSO] first appeared in Firefox 7 and is still a problem. According to comment 55, starting in Firefox 10 it causes a hang at startup rather than a crash. Ref: http://kb.mozillazine.org/Firefox_crashes#Crash_when_starting_Firefox <blockquote>Crashes at startup can occur in Firefox 7 or above (but not Firefox 6 or earlier) if you are using a corporate login system such as IBM Tivoli Access Manager or Oracle Enterprise Single Sign On Manager ([https://bugzilla.mozilla.org/show_bug.cgi?id=680927 bug 680927]). See the bug report for a suggested workaround (details [https://support.mozilla.org/en-US/questions/906287 here]), apply the fix from Oracle (see [https://bugzilla.mozilla.org/show_bug.cgi?id=680927#c58 bug comments 58-61]) or downgrade to Firefox 3.6.xx (available [http://www.mozilla.org/firefox/all-older.html here]) which is still being maintained. '''Note that, starting in Firefox 10, the same bug causes Firefox to hang at startup, rather than crash, with the process running in the background consuming CPU.'''</blockquote>
  7. AliceWyman said

    Cww, Could you include bug reports for the top issues? For example, for:
    2. Silverlight 5 (Netflix) may not work with some graphics cards on Macs
    ...I found this bug for 9.0.1 (Is there a new bug for Fx 10?):
    Bug 715396 - [Mac] Netflix not playing videos using 9.0.1 with some hardware

    In general, I try to avoid using bug numbers in these rollups because they've gotten public in the past and then it just drives unproductive traffic to bugs.

    My apologies about the confusion, I was under the impression that the Netflix breaking was fixed and so when it came up as a known issue in a meeting, I noted it as a new thing (having completely forgotten about it by that point)

    ''AliceWyman [[#post-44881|said]]'' <blockquote> '''Cww''', Could you include bug reports for the top issues? For example, for:<br> 2. Silverlight 5 (Netflix) may not work with some graphics cards on Macs<br> ...I found this bug for 9.0.1 (Is there a new bug for Fx 10?): <br> [https://bugzilla.mozilla.org/show_bug.cgi?id=715396 Bug 715396] - [Mac] Netflix not playing videos using 9.0.1 with some hardware<br> </blockquote> In general, I try to avoid using bug numbers in these rollups because they've gotten public in the past and then it just drives unproductive traffic to bugs. My apologies about the confusion, I was under the impression that the Netflix breaking was fixed and so when it came up as a known issue in a meeting, I noted it as a new thing (having completely forgotten about it by that point)
  8. scoobidiver said

    Cww said
    There may be an issue where the caret (the bar that marks where you're typing, also called the cursor) disappears so you can't tell where you're typing. This may have something to do with having plugins open (possibly in a background tab).

    This issue happens to me regularly in Fx 9 so it's not a regression from Fx 10.

    Really? We've definitely seen a spike in reports during the beta period. Do you have steps to reproduce?

    ''scoobidiver [[#post-44883|said]]'' <blockquote> ''Cww [[#post-44879|said]]'' <blockquote> There may be an issue where the caret (the bar that marks where you're typing, also called the cursor) disappears so you can't tell where you're typing. This may have something to do with having plugins open (possibly in a background tab). </blockquote> This issue happens to me regularly in Fx 9 so it's not a regression from Fx 10. </blockquote> Really? We've definitely seen a spike in reports during the beta period. Do you have steps to reproduce?
  9. AliceWyman said

    Bug 680927 - Startup crash in mozcomp.dll with Oracle Enterprise, F5 Networks, Passlogix V-GO, IBM Tivoli Access Manager SSO first appeared in Firefox 7 and is still a problem. According to comment 55, starting in Firefox 10 it causes a hang at startup rather than a crash.

    Hmmm... I'll pass this on to the enterprise people.

    EDIT: Nevermind, the fix came from Oracle, any enterprise likely to keep users up to date on ESR should stay up to date on other software too.

    ''AliceWyman [[#post-44884|said]]'' <blockquote> [https://bugzilla.mozilla.org/show_bug.cgi?id=680927 Bug 680927 - Startup crash in mozcomp.dll with Oracle Enterprise, F5 Networks, Passlogix V-GO, IBM Tivoli Access Manager SSO] first appeared in Firefox 7 and is still a problem. According to comment 55, starting in Firefox 10 it causes a hang at startup rather than a crash. </blockquote> Hmmm... I'll pass this on to the enterprise people. EDIT: Nevermind, the fix came from Oracle, any enterprise likely to keep users up to date on ESR should stay up to date on other software too.

    Modified by Cheng Wang on

  10. Cww said

    scoobidiver said
    This issue happens to me regularly in Fx 9 so it's not a regression from Fx 10.

    Really? We've definitely seen a spike in reports during the beta period. Do you have steps to reproduce?

    It happened from time to time while I was editing some French articles with many open tabs, but I have no STR. I think it's much older than Fx 9.

    ''Cww [[#post-44901|said]]'' <blockquote> ''scoobidiver [[#post-44883|said]]'' <blockquote> This issue happens to me regularly in Fx 9 so it's not a regression from Fx 10. </blockquote> Really? We've definitely seen a spike in reports during the beta period. Do you have steps to reproduce? </blockquote> It happened from time to time while I was editing some French articles with many open tabs, but I have no STR. I think it's much older than Fx 9.
  11. Cww said

    3. The two-digit user agent may confuse some websites and users may get notifications that their browser is out-of-date. Please get URLs and we'll try to work with the sites to correct this.

    What should the official advice be to prevent or workaround this sort of problem. A user has resorted to regressing to Firefox 9, finding that failed then doing a system restore.

    Where available do extensions to adjust User Id String prevent this problem, and are we recommending any such extensions, or even developing one as a short term fix. Presumably this problem will occur on all OS.

    I have not even attempted to read up on this but presumably this is not a bug, it is a problem after a decision to change version numbering and the ID string. Presuming that is the case have we publicised that widely in advance, and if so where.

    silkphoenix in /questions/916482

    .... Pay special attention to 1st item in KNOWN ISSUES. After I upgraded to FF 10.0, some of my websites gave me a warning that I need to use an UPDATED version of Firefox. Obviously, they couldn't recognize the two-digit version number. So I revert back to FF 9.0. But when I went to those websites, they still gave me the same warning even I have deleted the cookies, etc. I did a System Restore back to yesterday and now everything is back to normal. ....
    ''Cww [[#post-44879|said]]'' <blockquote> 3. The two-digit user agent may confuse some websites and users may get notifications that their browser is out-of-date. Please get URLs and we'll try to work with the sites to correct this. </blockquote> What should the official advice be to prevent or workaround this sort of problem. A user has resorted to regressing to Firefox 9, finding that failed then doing a system restore. Where available do extensions to adjust User Id String prevent this problem, and are we recommending any such extensions, or even developing one as a short term fix. Presumably this problem will occur on all OS. I have not even attempted to read up on this but presumably this is not a bug, it is a problem after a decision to change version numbering and the ID string. Presuming that is the case have we publicised that widely in advance, and if so where. [https://support.mozilla.org/en-US/user/75471 silkphoenix] in [/questions/916482] <blockquote> .... Pay special attention to 1st item in KNOWN ISSUES. After I upgraded to FF 10.0, some of my websites gave me a warning that I need to use an UPDATED version of Firefox. Obviously, they couldn't recognize the two-digit version number. So I revert back to FF 9.0. But when I went to those websites, they still gave me the same warning even I have deleted the cookies, etc. I did a System Restore back to yesterday and now everything is back to normal. .... </blockquote>
  12. Cww said

    AliceWyman said
    Cww, Could you include bug reports for the top issues? For example, for:
    2. Silverlight 5 (Netflix) may not work with some graphics cards on Macs
    ...I found this bug for 9.0.1 (Is there a new bug for Fx 10?):
    Bug 715396 - [Mac] Netflix not playing videos using 9.0.1 with some hardware

    In general, I try to avoid using bug numbers in these rollups because they've gotten public in the past and then it just drives unproductive traffic to bugs.

    My apologies about the confusion, I was under the impression that the Netflix breaking was fixed and so when it came up as a known issue in a meeting, I noted it as a new thing (having completely forgotten about it by that point)

    http://www.mozilla.org/en-US/firefox/10.0/releasenotes/ includes links to bug reports, including the Silverlight 5 (Netflix) bug, under Known issues. It just doesn't list bug reports for all of the issues you posted. I suppose I could do a bugzilla search (for example, on #5. OSX 10.5 Flip4Mac plugin crash). but it would be easier if you posted at least the bug numbers, if not a link, so that we can read through the reports to find available workarounds, in case the issue comes up on the forums.

    I see that Latest Firefox issues has been updated for Firefox 10 and includes the Silverlight 5 (Netflix) workaround. It doesn't mention the Flip4Mac plugin crash on OSX 10.5

    ''Cww [[#post-44900|said]]'' <blockquote> ''AliceWyman [[#post-44881|said]]'' <blockquote> '''Cww''', Could you include bug reports for the top issues? For example, for:<br> 2. Silverlight 5 (Netflix) may not work with some graphics cards on Macs<br> ...I found this bug for 9.0.1 (Is there a new bug for Fx 10?): <br> [https://bugzilla.mozilla.org/show_bug.cgi?id=715396 Bug 715396] - [Mac] Netflix not playing videos using 9.0.1 with some hardware<br> </blockquote> In general, I try to avoid using bug numbers in these rollups because they've gotten public in the past and then it just drives unproductive traffic to bugs. My apologies about the confusion, I was under the impression that the Netflix breaking was fixed and so when it came up as a known issue in a meeting, I noted it as a new thing (having completely forgotten about it by that point) </blockquote> http://www.mozilla.org/en-US/firefox/10.0/releasenotes/ includes links to bug reports, including the Silverlight 5 (Netflix) bug, under Known issues. It just doesn't list bug reports for all of the issues you posted. I suppose I could do a bugzilla search (for example, on #5. OSX 10.5 Flip4Mac plugin crash). but it would be easier if you posted at least the bug numbers, if not a link, so that we can read through the reports to find available workarounds, in case the issue comes up on the forums. I see that [[Latest Firefox issues]] has been updated for Firefox 10 and includes the Silverlight 5 (Netflix) workaround. It doesn't mention the Flip4Mac plugin crash on OSX 10.5
  13. Cww said

    .... The forward button is now conditional. That is, if there is nothing to go forward to, it will be hidden. (Only if you use big buttons). This may cause some confusion with users. .....

    I note if anyone wants two separate buttons it is much like the reload/stop button, it is customisable and easy to get two buttons if required, as demonstrated already by the-edeister & iMarshmellow with screenshots in /questions/916489#answer-304899

    ''Cww [[#post-44879|said]]'' <blockquote> .... The forward button is now conditional. That is, if there is nothing to go forward to, it will be hidden. (Only if you use big buttons). This may cause some confusion with users. ..... </blockquote> I note if anyone wants two separate buttons it is much like the reload/stop button, it is customisable and easy to get two buttons if required, as demonstrated already by ''the-edeister'' & ''iMarshmellow'' with screenshots in [/questions/916489#answer-304899]
  14. AliceWyman said

    http://www.mozilla.org/en-US/firefox/10.0/releasenotes/ includes links to bug reports, including the Silverlight 5 (Netflix) bug, under Known issues. It just doesn't list bug reports for all of the issues you posted. I suppose I could do a bugzilla search (for example, on #5. OSX 10.5 Flip4Mac plugin crash). but it would be easier if you posted at least the bug numbers, if not a link, so that we can read through the reports to find available workarounds, in case the issue comes up on the forums. I see that Latest Firefox issues has been updated for Firefox 10 and includes the Silverlight 5 (Netflix) workaround. It doesn't mention the Flip4Mac plugin crash on OSX 10.5

    I'll keep this in mind for next time. The Flip4Mac crash is bug 711564. There's no good workaround (imagining, of course, that users actually want to use the plugin) -- in a few days, the best workaround will be to update to the beta channel as there's a fix in place.

    ''AliceWyman [[#post-44917|said]]'' <blockquote> http://www.mozilla.org/en-US/firefox/10.0/releasenotes/ includes links to bug reports, including the Silverlight 5 (Netflix) bug, under Known issues. It just doesn't list bug reports for all of the issues you posted. I suppose I could do a bugzilla search (for example, on #5. OSX 10.5 Flip4Mac plugin crash). but it would be easier if you posted at least the bug numbers, if not a link, so that we can read through the reports to find available workarounds, in case the issue comes up on the forums. I see that [[Latest Firefox issues]] has been updated for Firefox 10 and includes the Silverlight 5 (Netflix) workaround. It doesn't mention the Flip4Mac plugin crash on OSX 10.5 </blockquote> I'll keep this in mind for next time. The Flip4Mac crash is bug 711564. There's no good workaround (imagining, of course, that users actually want to use the plugin) -- in a few days, the best workaround will be to update to the beta channel as there's a fix in place.
  15. Norton released Patch for Firefox 10 :) * http://community.norton.com/t5/Norton-Internet-Security-Norton/Firefox-10-Support-for-Norton-Toolbar/td-p/648241
  16. What is the status about ESR and Sync support?

    That looks pretty important to me, so why wasn't that included in the ESR section in the first post?

    What is the status about ESR and Sync support? *https://wiki.mozilla.org/Support/Weekly_Meetings/Notes_2012-01-23 "ESR may not support Sync" That looks pretty important to me, so why wasn't that included in the ESR section in the first post?
  17. In the French support forum, many users reported wrong website display (e.g. missing header) after updating. Clearing the cache fixes the problem.

    In the French support forum, many users reported wrong website display (e.g. missing header) after updating. Clearing the cache fixes the problem.
  18. Cww said

    The two-digit user agent may confuse some websites and users may get notifications that their browser is out-of-date. Please get URLs and we'll try to work with the sites to correct this.

    Related discussion:
    https://support.mozilla.org/en-US/forums/contributors/708130 Report Here: Websites or Applications reporting Firefox 10.0 as incompatible - might be a UA double-digit issue

    ''Cww [[#post-44879|said]]'' <blockquote> The two-digit user agent may confuse some websites and users may get notifications that their browser is out-of-date. Please get URLs and we'll try to work with the sites to correct this. </blockquote> Related discussion:<br> https://support.mozilla.org/en-US/forums/contributors/708130 ''Report Here: Websites or Applications reporting Firefox 10.0 as incompatible - might be a UA double-digit issue''
  19. cor-el said

    What is the status about ESR and Sync support? That looks pretty important to me, so why wasn't that included in the ESR section in the first post?

    Just to clarify, when I mentioned that ESR may not support Sync I meant that future releases of Firefox 10 that are meant to be used by enterprises and large organizations may not support Sync if Firefox 13 or higher break the backwards compatibility.

    In other words, whenever it's confirmed that a newer version will break the actual version of Firefox Sync (because the adoption of BrowserID) we will decide if we switch of Sync for Firefox 10.X to avoid confusion.

    ''cor-el [[#post-44951|said]]'' <blockquote> What is the status about ESR and Sync support? *https://wiki.mozilla.org/Support/Weekly_Meetings/Notes_2012-01-23 "ESR may not support Sync" That looks pretty important to me, so why wasn't that included in the ESR section in the first post? </blockquote> Just to clarify, when I mentioned that ESR may not support Sync I meant that future releases of Firefox 10 that are meant to be used by enterprises and large organizations may not support Sync if Firefox 13 or higher break the backwards compatibility. In other words, whenever it's confirmed that a newer version will break the actual version of Firefox Sync (because the adoption of BrowserID) we will decide if we switch of Sync for Firefox 10.X to avoid confusion.
  20. In the French version of Latest Firefox issues, I added the cache format issue and clarified the impacted GPU (AMD HD Radeon 62xx/63xx) for crashes.

    Many Mac OS X 10.4 French users with an Intel processor complained that Firefox 10 doesn't work while they were able to make Firefox 9 work although it should not.

    In the French version of [[Latest Firefox issues]], I added the cache format issue and clarified the impacted GPU (AMD HD Radeon 62xx/63xx) for crashes. Many Mac OS X 10.4 French users with an Intel processor complained that Firefox 10 doesn't work while they were able to make Firefox 9 work although it should not.
  1. 1
  2. 2
  3. 3