当サイトはユーザー体験を改善するためのメンテナンスを実施中に機能が制限される予定です。記事を読んでもあなたの問題が解決せず質問をしたい場合は、Twitter の @FirefoxSupport、Reddit の /r/firefox で、サポートコミュニティが皆さんを助けようと待機しています。

Mozilla サポートの検索

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

詳しく学ぶ

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

I have the latest version, but constantly getting messages that I'm outdated.

  • 3 件の返信
  • 2 人がこの問題に困っています
  • 5 回表示
  • 最後の返信者: bosko2

more options

I've got the latest version of firefox installed, yet I'm constantly getting messages that it's outdated - on Mozilla's site as well as many others.

I've deleted almost all of my plugins and extensions (and updated those I do use - though the Moz update your plugings page seems to have trouble with Shockwave Flash as well) ... and I still get the error.

The only thing I can think of is that I've somehow been too aggressive with my NoScript forbidding.

I've got the latest version of firefox installed, yet I'm constantly getting messages that it's outdated - on Mozilla's site as well as many others. I've deleted almost all of my plugins and extensions (and updated those I do use - though the Moz update your plugings page seems to have trouble with Shockwave Flash as well) ... and I still get the error. The only thing I can think of is that I've somehow been too aggressive with my NoScript forbidding.

選ばれた解決策

Thanks, resetting the user agent as per the article seems to have solved it.

(the modified one that needed reset was general:extra:microsoftdotnet )

この回答をすべて読む 👍 0

すべての返信 (3)

more options

Make sure that you are using Firefox 10? See Find what version of Firefox you are using to find your Firefox version, Latest version can be found here

You may need to reset your user agent as outlined in the article below.

more options

Yes, as I mentioned I have the latest version - uninstalled and reinstalled, even.

I'll try resetting the useragent.

more options

選ばれた解決策

Thanks, resetting the user agent as per the article seems to have solved it.

(the modified one that needed reset was general:extra:microsoftdotnet )