Windows 10 reached EOS (end of support) on October 14, 2025. For more information, see this article.

We’ve made the tough decision to shut down Monitor Plus on December 17, 2025. This means the data broker scan and automated removal service will no longer be available for Monitor Plus and Privacy Protection Plan customers. For more information, see the article Monitor Plus is shutting down – what you need to know.

Mozilla サポートの検索

サポート詐欺に注意してください。 私たちはあなたに通話やショートメッセージの送信、個人情報の共有を求めることはありません。疑わしい行為を見つけたら「迷惑行為を報告」からご報告ください。

詳しく学ぶ

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

Using event.type in ajax is the error

  • 1 件の返信
  • 1 人がこの問題に困っています
  • 6 回表示
  • 最後の返信者: guigs

more options

I would like to submit a fix to all the ajax problems on converting or fixing any ajax issues. When you are having trouble with a ajax request with Firefox first thing you need to do is look for any event.type within the responses. if you're using any to trigger on ready be sure to change them over to the default names of the same Id used to check ready state. for example what i noticed with them are Google chrome allows event.type to return the required id and all. Firefox does not. So here is the example...

Sent out ajax request. returned it with... ajax_blah.onreadystatechange=function(){ /*event.type.readyState does not work in Firefox but does in chrome*/ /*ajax_blah.readyState works onGoogle chrome and Firefox */ if(ajax_blah.readyState==4 && ajax_blah.status==200){ /*fire*/ } }


So Anyways quit using events unless you find a alt small fix. function(event) may help? you tell me but i wanted to help people searching for a fix. Enjoy

I would like to submit a fix to all the ajax problems on converting or fixing any ajax issues. When you are having trouble with a ajax request with Firefox first thing you need to do is look for any event.type within the responses. if you're using any to trigger on ready be sure to change them over to the default names of the same Id used to check ready state. for example what i noticed with them are Google chrome allows event.type to return the required id and all. Firefox does not. So here is the example... Sent out ajax request. returned it with... ajax_blah.onreadystatechange=function(){ /*event.type.readyState does not work in Firefox but does in chrome*/ /*ajax_blah.readyState works onGoogle chrome and Firefox */ if(ajax_blah.readyState==4 && ajax_blah.status==200){ /*fire*/ } } So Anyways quit using events unless you find a alt small fix. function(event) may help? you tell me but i wanted to help people searching for a fix. Enjoy

すべての返信 (1)

more options

Locking, good find! Have you considered filing a bug as well?