SUMO community discussions

Firefox 29 Release / Issues / Status

  • 48 Replies
  • Last reply by user633449
  1. user633449
    user633449 503 posts
    more options

    Happy Firefox 29 week! The week we've all been anxiously waiting for sometime is finally here! The new Firefox design is now live. We will be launching this release somewhat differently than other releases. We will be launching this release slower than other releases, an watching feedback very closely. As this is such a major release I won't go through all the major changes in this post, but please keep an eye out for feedback and issues related to both the new design, the update process (including the tour), and Firefox accounts.

    Thanks all!

    Happy Firefox 29 week! The week we've all been anxiously waiting for sometime is finally here! The new Firefox design is now live. We will be launching this release somewhat differently than other releases. We will be launching this release slower than other releases, an watching feedback very closely. As this is such a major release I won't go through all the major changes in this post, but please keep an eye out for feedback and issues related to both the new design, the update process (including the tour), and Firefox accounts. Thanks all!
  2. philipp
    philipp 1281 posts
    more options

    the most popular weather extension forecastfox isn't compatible with firefox 29 yet...

    the most popular weather extension forecastfox isn't compatible with firefox 29 yet...
  3. user633449
    user633449 503 posts
    more options

    Just an FYI that 29 was released today for manual updates only.

    Just an FYI that 29 was released today for manual updates only.
  4. John99
    John99 3665 posts
    more options

    Minor glitch with Sync accounts. Users without en-US not able to register, but apparently being fixed right now on the Sync side.

    I also noted the addon NoScript may block the correct functioning of initial logon from the about:accounts registration page.

    Minor glitch with Sync accounts. Users without en-US not able to register, but apparently being fixed right now on the Sync side. * [https://bugzilla.mozilla.org/show_bug.cgi?id=1001686 Bug 1001686 - Sync about:accounts page is blank] * UPDATE bug re-titled, re-purposed and re-opened <br /> ''Bug 1001686 - Add more informative messaging when a Legacy Sync user opens about:accounts page (currently it's blank) '' I also noted the addon NoScript may block the correct functioning of initial logon from the about:accounts registration page.

    Modified by John99 on

  5. Underpass
    Underpass 773 posts
    more options

    I experienced the blank Firefox account page myself. It turned out that it was a cookie problem: I surf the web with the cookies disabled. I had to add firefox.com in the exceptions and the problem went out.

    Now I'm experiencing the toolbar reset....

    https://support.mozilla.org/it/questions/997381

    (N.B. For anyone not wishing to use Italian, then to stay within your own locale try link /questions/997381 ~J99 )

    I experienced the blank Firefox account page myself. It turned out that it was a cookie problem: I surf the web with the cookies disabled. I had to add firefox.com in the exceptions and the problem went out. Now I'm experiencing the toolbar reset.... https://support.mozilla.org/it/questions/997381 (N.B. For anyone not wishing to use Italian, then to stay within your own locale try link [/questions/997381] ~J99 )

    Modified by John99 on

  6. philipp
    philipp 1281 posts
    more options

    there seems to be an issue where prints from inside pdf.js in firefox 29 inly produce blank pages:

    https://support.mozilla.org/questions/996487
    https://support.mozilla.org/questions/997170
    https://support.mozilla.org/questions/997325

    edit: see bug #999284

    there seems to be an issue where prints from inside pdf.js in firefox 29 inly produce blank pages: https://support.mozilla.org/questions/996487 <br>https://support.mozilla.org/questions/997170 <br>https://support.mozilla.org/questions/997325 edit: see [https://bugzilla.mozilla.org/show_bug.cgi?id=999284 bug #999284]

    Modified by philipp on

  7. jscher2000 - Support Volunteer
    jscher2000 - Support Volunteer 807 posts
    more options

    Address bar weird display artifacts caused by RSS Icon extension:

    Address bar weird display artifacts caused by RSS Icon extension: * [https://support.mozilla.org/questions/997292 Address bar changes to wingdings type font] * [https://support.mozilla.org/questions/997324 problem with upgrade to 29.0 - address/search bar overlaid with icons]
  8. user633449
    user633449 503 posts
    more options

    Hey all! We will be releasing a 29.0.1 this week (most likely Friday) to correct the following Issues:

    Desktop Known Issues:

    • 1003707 – pdf.js print prints a white page - this has a backout option and is the 'driver' of the desktop dot release
    • 1001167 – Session Restore doesn't handle a corrupted sessionstore.js file properly - patch ready, low risk, regression new to 29
    • 907373 – -moz-os-version media query is not working on Windows 8.1 - patch ready, low risk, helps users with dark themes on Windows
    • 1005958– Disable seer until new backend is rewritten - patch ready, lower risk workaround for shutdown hangs in bug 966469

    Mobile Known Issues:

    • 1005074 – Re-enable 'Send Tab to Devices' on Beta and Release with a string swap -- has a low risk patch, this is the 'driver' for our non-urgent dot release
    • 987867 – JB & KK crash in java.util.ConcurrentModificationException: at java.util.LinkedList$LinkIterator.next(LinkedList.java) - has patch, fixes reproducible crash, verified on Beta
    • 1003897 – Character Encoding selection broken in Fennec 29 - has a verified backout

    linkified bug reports. aw

    Hey all! We will be releasing a 29.0.1 this week (most likely Friday) to correct the following Issues: '''Desktop Known Issues''': * [https://bugzilla.mozilla.org/show_bug.cgi?id=1003707 1003707] – pdf.js print prints a white page - this has a backout option and is the 'driver' of the desktop dot release * [https://bugzilla.mozilla.org/show_bug.cgi?id=1001167 1001167] – Session Restore doesn't handle a corrupted sessionstore.js file properly - patch ready, low risk, regression new to 29 * [https://bugzilla.mozilla.org/show_bug.cgi?id=907373 907373] – -moz-os-version media query is not working on Windows 8.1 - patch ready, low risk, helps users with dark themes on Windows * [https://bugzilla.mozilla.org/show_bug.cgi?id=1005958 1005958]– Disable seer until new backend is rewritten - patch ready, lower risk workaround for shutdown hangs in [https://bugzilla.mozilla.org/show_bug.cgi?id=966469 bug 966469] '''Mobile Known Issues''': * [https://bugzilla.mozilla.org/show_bug.cgi?id=1005074 1005074] – Re-enable 'Send Tab to Devices' on Beta and Release with a string swap -- has a low risk patch, this is the 'driver' for our non-urgent dot release * [https://bugzilla.mozilla.org/show_bug.cgi?id=987867 987867] – JB & KK crash in java.util.ConcurrentModificationException: at java.util.LinkedList$LinkIterator.next(LinkedList.java) - has patch, fixes reproducible crash, verified on Beta * [https://bugzilla.mozilla.org/show_bug.cgi?id=1003897 1003897] – Character Encoding selection broken in Fennec 29 - has a verified backout <sub> linkified bug reports. aw</sub>

    Modified by AliceWyman on

  9. John99
    John99 3665 posts
    more options

    Bookmarks
    Automated backups have changed, as advised by user Axis in

    '''Bookmarks''' <br />Automated backups have changed, as advised by user [https://support.mozilla.org/en-US/user/649506 Axis] in *''No more automatic backup of bookmarks since FF 29/30 ?'' [/questions/999068#answer-570033] ** [https://bugzilla.mozilla.org/show_bug.cgi?id=983988 Bug 983988 - bookmark backups .json files not being generated often enough on some systems where idle is "bogus"] * and "Firefox 29 is no longer automatically creating bookmarks backups." [/questions/998682]
  10. FredMcD
    FredMcD 923 posts
    more options

    Good day all. I was reading some of the postings here and I notice something. It was mentioned on several threads that Firefox v29 would only update manually. In my case, I had opened the About Firefox window, and the download started right way. There was no option to not upgrade.

    About Forecastfox and other add-ons. Many use the add-on bar by default. While some icons can find new homes, others can't.

    Also, I found that after Firefox v29, a LOT of my settings and
    add-ons were changed / reset. Even the Hardware Acceleration had to be reset as something had turned it on.

    Good day all. I was reading some of the postings here and I notice something. It was mentioned on several threads that Firefox v29 would only update manually. In my case, I had opened the About Firefox window, and the download started right way. There was no option to not upgrade.<BR><BR> About Forecastfox and other add-ons. Many use the add-on bar by default. While some icons can find new homes, others can't.<BR><BR> Also, I found that after Firefox v29, a LOT of my settings and<BR> add-ons were changed / reset. Even the Hardware Acceleration had to be reset as something had turned it on.
  11. John99
    John99 3665 posts
    more options

    There must be millions that can not use Firefox because of hangs, and many of those will not be the seer / netpredictions.sqlite issue with a chemspill workaround.

    Allowing History to be saved may well solve the issue, but is obviously not something the users affected will do. I am having to agree they are better off using Chrome than Firefox 28 e.g. /questions/997448?page=3#answer-570788

    There must be millions that can not use Firefox because of hangs, and many of those will not be the seer / netpredictions.sqlite issue with a chemspill workaround. Allowing History to be saved may well solve the issue, but is obviously not something the users affected will do. I am having to agree they are better off using Chrome than Firefox 28 e.g. [/questions/997448?page=3#answer-570788]
  12. Underpass
    Underpass 773 posts
    more options

    @john99: we are suggesting upset people to switch to Firefox ESR waiting for version 32 (Australis) to became the new ESR.

    https://www.mozilla.org/en-US/firefox/organizations/faq/

    I'd rather not suggest them to switch to Chrome.

    @john99: we are suggesting upset people to switch to Firefox ESR waiting for version 32 (Australis) to became the new ESR. https://www.mozilla.org/en-US/firefox/organizations/faq/ I'd rather not suggest them to switch to Chrome.

    Modified by Underpass on

  13. John99
    John99 3665 posts
    more options

    Hi Simone,
    Thanks for the suggestion.

    I had thought of that. I am not sure what the best course of action is other than , sort out STR for this sub issue and get it fixed quickly. At least once we have STR and a confirmed bug we know what we are dealing with.

    I have sometimes suggested ESR but I am not sure that is the best option here.

    If they are getting the fix in the chemspill they can fix it themselves right now simply by toggling a pref. It is easier and leaves them on the Release channel.

    If they have the other issue they only delay the inevitable and get mixed up trying EST. Again there is a simple work around allow Firefox to save History on closedown by using New Button ->Prefs -> save history . I also point out Private Browsing windows are still available.

    I have for a long while selectively suggested using ESR on occasions, but I try to do that very carefully and not where I think there are better workarounds.

    If everyone agrees suggesting ESR in this case is to be the official solution, or a better solution than agreeing an alternative browser be used I will of course go with that.

    Hi Simone, <br /> Thanks for the suggestion. I had thought of that. I am not sure what the best course of action is other than , sort out STR for this sub issue and get it fixed quickly. At least once we have STR and a confirmed bug we know what we are dealing with. I have sometimes suggested ESR but I am not sure that is the best option here. If they are getting the fix in the chemspill they can fix it themselves right now simply by toggling a pref. It is easier and leaves them on the Release channel. If they have the other issue they only delay the inevitable and get mixed up trying EST. Again there is a simple work around allow Firefox to save History on closedown by using New Button ->Prefs -> save history . I also point out Private Browsing windows are still available. I have for a long while selectively suggested using ESR on occasions, but I try to do that very carefully and not where I think there are better workarounds. If everyone agrees suggesting ESR in this case is to be the official solution, or a better solution than agreeing an alternative browser be used I will of course go with that.
  14. Underpass
    Underpass 773 posts
    more options

    Version ESR receives all the Firefox security updates: IMHO it is the best choice for people who are experiencing problem with extensions, bugs and the sort issues that might occur when a major release breaks in.

    Version ESR receives all the Firefox security updates: IMHO it is the best choice for people who are experiencing problem with extensions, bugs and the sort issues that might occur when a major release breaks in.
  15. Gingerbread Man
    Gingerbread Man 46 posts
    more options

    jscher2000 said

    Address bar weird display artifacts caused by RSS Icon extension:

    From what I can see, this is the only replacement that works:

    Also beware ShowIP 2.4 which incorrectly states "ready for Firefox 29" in the release notes.

    ''jscher2000 [[#post-59239|said]]'' <blockquote> Address bar weird display artifacts caused by RSS Icon extension: </blockquote> From what I can see, this is the only replacement that works: * https://addons.mozilla.org/firefox/addon/rss-icon-in-url-bar/ Also beware [https://addons.mozilla.org/firefox/addon/showip/ ShowIP 2.4] which incorrectly states "ready for Firefox 29" in the release notes. * https://addons.mozilla.org/firefox/addon/showip/reviews/583682/
  16. Underpass
    Underpass 773 posts
    more options

    For me it turned out that that extension too causes problems (it "locks" the toolbar in a way that you cannot add new items on it - it resets upon reboot) . So I suggest you to pay attention even to that addon.

    For me it turned out that that extension too causes problems (it "locks" the toolbar in a way that you cannot add new items on it - it resets upon reboot) . So I suggest you to pay attention even to that addon.
  17. user633449
    user633449 503 posts
    more options
    It was mentioned on several threads that Firefox v29 would only update manually

    This is because Firefox 29 updates are throttled until we release 29.0.1 tomorrow, then all users will update automatically.

    we are suggesting upset people to switch to Firefox ESR waiting for version 32 (Australis) to became the new ESR.

    Please do not suggest ESR. ESR fails in several aspects:

    • It doesn't receive all security updates that release does.
    • We do not provide support for it. It is meant for environments with a dedicated IT staff, not for home users
    • In a few versions ESR uses will get updated to Australis, this is just delaying the inevitable.

    If users want to switch to chrome (which is less customizable than Firefox so I don't understand why you would if you are upset with Firefox UI Changes)let them switch to chrome. It's better than being on an out of date Firefox, and that's the value of the open web, being able to use the browser of your choice. Explain why they may want to stay with Firefox, but your time is better spent helping users who want to use Firefox than those who say "If you don't revert this change I'm switching to Chrome!!!"

    As for the hang on shutdown issues, we fixed one case that was common in Firefox 29.0.1. QA hasn't had any luck trying to reproduce the other steps, so if you see this issue with 29.0.1 tomorrow please let me know and we can file more bugs.

    <blockquote> It was mentioned on several threads that Firefox v29 would only update manually </blockquote> This is because Firefox 29 updates are throttled until we release 29.0.1 tomorrow, then all users will update automatically. <blockquote> we are suggesting upset people to switch to Firefox ESR waiting for version 32 (Australis) to became the new ESR. </blockquote> Please do not suggest ESR. ESR fails in several aspects: * It doesn't receive all security updates that release does. * We do not provide support for it. It is meant for environments with a dedicated IT staff, not for home users * In a few versions ESR uses will get updated to Australis, this is just delaying the inevitable. If users want to switch to chrome (which is less customizable than Firefox so I don't understand why you would if you are upset with Firefox UI Changes)let them switch to chrome. It's better than being on an out of date Firefox, and that's the value of the open web, being able to use the browser of your choice. Explain why they may want to stay with Firefox, but your time is better spent helping users who want to use Firefox than those who say "If you don't revert this change I'm switching to Chrome!!!" As for the hang on shutdown issues, we fixed one case that was common in Firefox 29.0.1. QA hasn't had any luck trying to reproduce the other steps, so if you see this issue with 29.0.1 tomorrow please let me know and we can file more bugs.
  18. AliceWyman
    AliceWyman 6161 posts
    more options

    Tyler Downer said

    Please do not suggest ESR. ESR fails in several aspects:
    • It doesn't receive all security updates that release does.

    Are you saying that the latest Firefox ESR is less secure than the latest Firefox release?

    It could be that some of the security updates for the latest release version are for vulnerabilities that don't affect the latest ESR version.

    ''Tyler Downer [[#post-59456|said]]'' <blockquote> Please do not suggest ESR. ESR fails in several aspects: * It doesn't receive all security updates that release does. </blockquote> Are you saying that the latest Firefox ESR is less secure than the latest Firefox release? It could be that some of the security updates for the latest release version are for [http://www.mozilla.org/security/known-vulnerabilities/ vulnerabilities] that don't affect the latest ESR version.

    Modified by AliceWyman on

  19. user633449
    user633449 503 posts
    more options

    ESR only receives Critical and High fixes, sometimes a moderate fix sneaks in but that isn't the norm.

    ESR only receives Critical and High fixes, sometimes a moderate fix sneaks in but that isn't the norm.
  20. John99
    John99 3665 posts
    more options

    Should we have a post mortem of any kind on this Release I have a couple of ideas about how the Release procedure may be improved.

    1. Find some method of advising users before the update about what will change.
    2. Have early adopters upgrade first. Have a method and deliberate policy of encouraging self selection for upgrading early. (Something more than just the manual check, some must inadvertently upgrade because of that.)

    The first point is to try to help with the problem of users that upgrade and find that addons are broken, the UI has changed or whatever, and not only do they not like it but they would prefer to manage the timing of the upgrade.
    Sure the new onboarding tour from within the browser is great and far better than just reading an article written about the new version, but that is no substitute from trying to prepare the user for the change.

    The second point is that we do not test with a big enough beta population. The majority of Releases have a Chemspill point Release. Possibly to a large extent who gets the new Release initially is probably a mix of luck and who is a heavy user. Can we not make a better method ?

    Why not at least allow users to choose in advance whether they get the release the first time it is offered, or wait until the release is un throttled the second time.

    Let's at least try to manage it so the early adoptors most able to cope with change get the first upgrades. Not the majority typical user that will in all probability struggle and complain; or worse give up and switch browsers; if anything at all goes wrong.

    Should we have a post mortem of any kind on this Release I have a couple of ideas about how the Release procedure may be improved. #Find some method of advising users before the update about what will change. #Have early adopters upgrade first. Have a method and deliberate policy of encouraging self selection for upgrading early. (Something more than just the manual check, some must inadvertently upgrade because of that.) The first point is to try to help with the problem of users that upgrade and find that addons are broken, the UI has changed or whatever, and not only do they not like it but they would prefer to manage the timing of the upgrade. <br /> Sure the new onboarding tour from within the browser is great and far better than just reading an article written about the new version, but that is no substitute from trying to prepare the user for the change. The second point is that we do not test with a big enough beta population. The majority of Releases have a Chemspill point Release. Possibly to a large extent who gets the new Release initially is probably a mix of luck and who is a heavy user. Can we not make a better method ? Why not at least allow users to choose in advance whether they get the release the first time it is offered, or wait until the release is un throttled the second time. Let's at least try to manage it so the early adoptors most able to cope with change get the first upgrades. Not the majority typical user that will in all probability struggle and complain; or worse give up and switch browsers; if anything at all goes wrong.
  1. 1
  2. 2
  3. 3