Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Learn More

Toś ta nitka jo se zacyniła a archiwěrowała. Pšosym stajśo nowe pšašanje, joli trjebaśo pomoc.

Using event.type in ajax is the error

  • 1 wótegrono
  • 1 ma toś ten problem
  • 45 naglědow
  • Slědne wótegrono wót 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

Wšykne wótegrona (1)

more options

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