SUMO community discussions

Firefox 11 issues thread (and status updates)

  1. The article was just written for NVIDIA to link to as almost no one has that setup... we haven't seen any feedback with regards to this problem either.

    We probably should document all of these things in the Latest Issues article. Want to head that project up, Alice?

    The article was just written for NVIDIA to link to as almost no one has that setup... we haven't seen any feedback with regards to this problem either. We probably should document all of these things in the Latest Issues article. Want to head that project up, Alice?
  2. What do you mean by "document all of these things in the Latest Issues article" ... post links to new Firefox 11 articles in the Firefox 11 section of latest Firefox issues? I think the person who approved the new article should do that, since how would I know when new articles are created?

    What do you mean by "document all of these things in the Latest Issues article" ... post links to new Firefox 11 articles in the Firefox 11 section of [[latest Firefox issues]]? I think the person who approved the new article should do that, since how would I know when new articles are created?
  3. I actually meant take the top of this thread and make sure that the latest issues article is updated to reflect the things in this thread.

    I actually meant take the top of this thread and make sure that the latest issues article is updated to reflect the things in this thread.
  4. I've written Some rich text editors do not work in Firefox 11 for the TinyMCE problem. Feel free to use it.

    I've written [[Some rich text editors do not work in Firefox 11]] for the TinyMCE problem. Feel free to use it.
  5. Other new issues:

    • Java - we are blocklisting old version of Java (hasn't happened yet). We should get this ready ahead of time. There is also a bug in Java for Mac that makes it sometimes not work.
    • TypeError: Components.classes[cid] (caused by add-ons) - this error happens on startup. You can ignore it or figure out what extension is causing it. We think the extensions keep working.
    • "Your browser is blocking Flash" - A change to Flash last week makes some flash version detection methods break. This affects Yahoo mail (also Att mail and others that are based on Yahoo). The solution is to switch to "classic mode" in the email program.
    Other new issues: *Java - we are blocklisting old version of Java (hasn't happened yet). We should get this ready ahead of time. There is also a bug in Java for Mac that makes it sometimes not work. * TypeError: Components.classes[cid] (caused by add-ons) - this error happens on startup. You can ignore it or figure out what extension is causing it. We think the extensions keep working. *"Your browser is blocking Flash" - A change to Flash last week makes some flash version detection methods break. This affects Yahoo mail (also Att mail and others that are based on Yahoo). The solution is to switch to "classic mode" in the email program.
  6. ''Verdi [[#post-46006|said]]'' <blockquote> "Your browser is blocking Flash" </blockquote> *https://support.mozilla.org/en-US/questions/924230 *https://support.mozilla.org/en-US/questions/924246 *https://support.mozilla.org/en-US/questions/924215 *https://support.mozilla.org/en-US/questions/924319 *https://support.mozilla.org/en-US/questions/924270 *https://support.mozilla.org/en-US/questions/924278 *https://support.mozilla.org/en-US/questions/924300
  7. Verdi said

    Other new issues:
    • Java - we are blocklisting old version of Java (hasn't happened yet). We should get this ready ahead of time. There is also a bug in Java for Mac that makes it sometimes not work.
    • TypeError: Components.classes[cid] (caused by add-ons) - this error happens on startup. You can ignore it or figure out what extension is causing it. We think the extensions keep working.
    • "Your browser is blocking Flash" - A change to Flash last week makes some flash version detection methods break. This affects Yahoo mail (also Att mail and others that are based on Yahoo). The solution is to switch to "classic mode" in the email program.

    Cheng and I documented these yesterday:

    ''Verdi [[#post-46006|said]]'' <blockquote> Other new issues: *Java - we are blocklisting old version of Java (hasn't happened yet). We should get this ready ahead of time. There is also a bug in Java for Mac that makes it sometimes not work. * TypeError: Components.classes[cid] (caused by add-ons) - this error happens on startup. You can ignore it or figure out what extension is causing it. We think the extensions keep working. *"Your browser is blocking Flash" - A change to Flash last week makes some flash version detection methods break. This affects Yahoo mail (also Att mail and others that are based on Yahoo). The solution is to switch to "classic mode" in the email program. </blockquote> Cheng and I documented these yesterday: *[[Using the Java plugin with Firefox]] - has a warning about blocking *[[Yahoo! and at&t mail say your browser is blocking Flash]] - new article *<strike>[[How to get rid of common Firefox popup TypeError messages]] - new article</strike> [[Fixing Firefox TypeError messages]] - update

    Modified by Michael Verdi on

  8. https://support.mozilla.org/en-US/questions/924241

    Is this a bug? Please note, the link in the post has to be copied without the trailing dot.

    https://support.mozilla.org/en-US/questions/924241 Is this a bug? Please note, the link in the post has to be copied without the trailing dot.
  9. Vivek.Wilfred said

    https://support.mozilla.org/en-US/questions/924241 Is this a bug? Please note, the link in the post has to be copied without the trailing dot.

    I don't think it is. I commented in the thread.

    ''Vivek.Wilfred [[#post-46016|said]]'' <blockquote> https://support.mozilla.org/en-US/questions/924241 Is this a bug? Please note, the link in the post has to be copied without the trailing dot. </blockquote> I don't think it is. I commented in the thread.
  10. Thank you.

    PS: That's new to me and very informative. My personal thanks.

    Thank you. PS: That's new to me and very informative. My personal thanks.
  11. See also [/questions/899292]

    See also [[/questions/899292]] *[https://bugzilla.mozilla.org/show_bug.cgi?id=354161 bug 354161] - DOM pruned at depth 200

    Modified by cor-el on

  12. Thanks cor-el.

    I've also sent a mail (http://www.edgewaysbooks.com/contact.html) explaining the site errors with a link to the W3C Validator.

    Thanks cor-el. I've also sent a mail (http://www.edgewaysbooks.com/contact.html) explaining the site errors with a link to the W3C Validator.
  13. Recently reinstalled Windows after acquiring a new virus, (I know, foolish), but noticed a repeat fault with Firefox now asking to save passwords nor using saved passwords from a backup file, there is a thread about it [/questions/760505] but the solution I was left with wasn't mentioned so I'll post it here for y'all.

    After tinkering an tottering and finding no fix, I wondered why my new installation had no option at all to enable/disable private browsing, I bashed about:config into a new tab and found 'browser.privatebrowsing.autostart' marked as true, with no option in the GUI to change it, changing this to false has solved the issue.

    This may also work for users who do have an option in the GUI but find that it is "greyed out" for whatever reason.

    Cheers, Ducklz.

    Recently reinstalled Windows after acquiring a new virus, (I know, foolish), but noticed a repeat fault with Firefox now asking to save passwords nor using saved passwords from a backup file, there is a thread about it [[/questions/760505]] but the solution I was left with wasn't mentioned so I'll post it here for y'all. After tinkering an tottering and finding no fix, I wondered why my new installation had no option at all to enable/disable private browsing, I bashed about:config into a new tab and found 'browser.privatebrowsing.autostart' marked as true, with no option in the GUI to change it, changing this to false has solved the issue. This may also work for users who do have an option in the GUI but find that it is "greyed out" for whatever reason. Cheers, Ducklz.
  14. The browser.privatebrowsing.autostart pref should follow the setting to "Always use private browsing mode" in "Tools > Options > Privacy" (Never remember history)
    If you can't change the latter then also check for a -private switch in the command line or an extension that forces or prevents PB mode.

    • Tools > Options > Privacy, choose the setting Firefox will: Use custom settings for history
      • [ ] "Always use private browsing mode"
    The <b>browser.privatebrowsing.autostart</b> pref should follow the setting to "Always use private browsing mode" in "Tools > Options > Privacy" (Never remember history)<br /> If you can't change the latter then also check for a -private switch in the command line or an extension that forces or prevents PB mode. *Tools > Options > Privacy, choose the setting <b>Firefox will: Use custom settings for history</b> **[ ] "Always use private browsing mode" *https://support.mozilla.org/kb/Private+Browsing

    Modified by cor-el on

  1. 1
  2. 2