S
Steve Wright
I have an AJAX routine on a webpage that is working in IE6, but not IE7
or Firefox v2.0.0.2
The webpage is
http://www.a-drop-in-the-ocean.co.uk/CWS/monitor10bins.php?quarry=401
The AJAX routine is encapsulated in the module
http://www.a-drop-in-the-ocean.co.uk/CWS/js/timer.js
What it is supposed to do is every ten seconds, read the contents of the
file http://www.a-drop-in-the-ocean.co.uk/CWS/401/seqno.txt. This file
just contains the number 46955. If this number changes then the page
will refresh.
The timer routine, counts down the 10 seconds, displaying the counter in
the top right hand corner. Once the counter hits zero, it triggers the
AJAX request.
The onload event also triggers the AJAX request to get the initial value
of the number.
I presume that IE7 and FF use the XMLHttpRequest() function and that I
must have coded this incorrectly. But what is wrong with it?
Interestingly, the firebug extension in FF, shows the request and
response headers along with the response 46955.
Fixing this is not critical at the moment as IE6 is our company
standard. But at some stage we will migrate to IE7...
Has anybody got any ideas?
or Firefox v2.0.0.2
The webpage is
http://www.a-drop-in-the-ocean.co.uk/CWS/monitor10bins.php?quarry=401
The AJAX routine is encapsulated in the module
http://www.a-drop-in-the-ocean.co.uk/CWS/js/timer.js
What it is supposed to do is every ten seconds, read the contents of the
file http://www.a-drop-in-the-ocean.co.uk/CWS/401/seqno.txt. This file
just contains the number 46955. If this number changes then the page
will refresh.
The timer routine, counts down the 10 seconds, displaying the counter in
the top right hand corner. Once the counter hits zero, it triggers the
AJAX request.
The onload event also triggers the AJAX request to get the initial value
of the number.
I presume that IE7 and FF use the XMLHttpRequest() function and that I
must have coded this incorrectly. But what is wrong with it?
Interestingly, the firebug extension in FF, shows the request and
response headers along with the response 46955.
Fixing this is not critical at the moment as IE6 is our company
standard. But at some stage we will migrate to IE7...
Has anybody got any ideas?