Hi Kaffeen. I typically hate it when people responding to a question try to
skirt the actual question and suggest an alternative approach instead, but
in this case I can't help but think to myself, "who cares what IE 6 does
anymore??? Just download IE 8 and press on!" . IE is already two versions
beyond 6, and 6 is renowned for being as far from standardized as a browser
could be, so investing the time to try and make IE 6 do ANYTHING correctly
is kind of...well, it IS, a waste of time in my opinion. Why not just
upgrade your browser and press on?
Oh, and while you're at it, I would highly suggest choosing a JS library
that has Ajax functionality built in and use that instead of trying to
manage such things manually. My favorite flavor is Prototype (
http://www.prototypejs.org/) . To do an Ajax call in Prototype that updates
the contents of a div, it's as easy as this:
<script>
new Ajax.Updater('mytargetdiv','
http://www.somedomain.com/ajaxResponse.php');
</script>
No need to worry about monitoring the request's state or ANYTHING else!
Doug :0)
On Sun, May 24, 2009 at 11:15 AM, kaffeen <[email protected]> wrote:
> First, I'm not sure if this group would be the correct one to use for this
> type of question. I've not really actively participated in this group,
> although I do read it frequently. My apologies if this is not the place for
> this, please let me know.
>
> Second, I have a bug in IE that I cannot seem to figure out. It is actually
> from a course on Lynda.com. I've not had much experience with Ajax, so I am
> taking one of those lessons there. This particular section of the lesson is
> related to the different states and status.
>
> The bug is related to the following snippet of code...
>
> function showState() {
> currMsg = document.getElementById("updateArea").innerHTML;
> document.getElementById("updateArea").innerHTML = currMsg + "<p>The
> current state is " + xhr.readyState + " and the status is " + xhr.status +
> "</p>";
> }
>
> Basically, this is just updating the browser with the status. In Firefox,
> it works fine and the output is as follows:
>
> *The current state is 1 and the status is 200*
>
> *The current state is 2 and the status is 200*
>
> *The current state is 3 and the status is 200*
>
> *The current state is 4 and the status is 200*
>
> In IE 6, I get this result (with an error):
>
> *The current state is 4 and the status is 200*
>
> If I examine the error, it is basically complaining about the
> document.getElementById("updateArea").innerHTML
>
> IE6 does not report any of the 1, 2, or 3 states.
>
> I don't have a Premium membership to Lynda, so it is quite possible there
> is a typo there, but I can't find it and it works fine with FF. In addition,
> I have googled this and found some things to try and interesting information
> about innerHTML and element/id bugs with IE, however, at this time, nothing
> has really resolved this particular error for me.
>
> If anyone understands this bug/error, please let me know how to correct in
> IE.
>
> Kind Regards,
>
> Kaffeen
>
>
> -- If you understand, things are just as they are. If you do not
> understand, things are just as they are.
>
>
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
Our Web site: http://www.RefreshAustin.org/
You received this message because you are subscribed to the Google Groups
"Refresh Austin" group.
[ Posting ]
To post to this group, send email to [email protected]
Job-related postings should follow http://tr.im/refreshaustinjobspolicy
We do not accept job posts from recruiters.
[ Unsubscribe ]
To unsubscribe from this group, send email to
[email protected]
[ More Info ]
For more options, visit this group at
http://groups.google.com/group/Refresh-Austin
-~----------~----~----~----~------~----~------~--~---
