Page 1 of 1

php, ajax and causes iexplore to hang.

Posted: Wed Sep 12, 2007 4:19 am
by ottootto
Hi.
I'm currently working on a classic html/php/javascript/ajax/mysql web project.
At the moment iexplore hangs when I dynamic update content. It's seem to happen rather random.
Firefox is unaffected, - I'm suspecting the $_SESSION is large(contains a lot of objects variables etc.).
Any help would be appriciaded to get rid of these hangs.
-otto

Posted: Wed Sep 12, 2007 4:27 am
by CoderGoblin
Never had the problem with IE although had it with Firefox and simultaneous requests. You may want to give us some more details (code examples, what you have tried to solve the problem etc) to assist us helping you.

Posted: Wed Sep 12, 2007 8:32 am
by superdezign
Does IE's console display any errors?

Posted: Fri Sep 14, 2007 3:30 am
by n00b Saibot
superdezign wrote:Does IE's console display any errors?
IE's console??? :?

Posted: Fri Sep 14, 2007 3:51 am
by superdezign
n00b Saibot wrote:IE's console??? :?
When a page has errors, IE shows a little yield sign in the corner which, when clicked on, will display the errors.

Posted: Fri Sep 14, 2007 4:14 am
by n00b Saibot
ahhh! hot here, confused...

I use Script Debugger from M$... cool to debug script errors...

Reason that i can think of this behavior are, either an infinite loop, or an update which happens while the page is still loading.

Posted: Sun Sep 16, 2007 4:09 pm
by Attilitus
There is likely something wrong with your javascript... We really cannot give you all that much assistance unless you post the code that you are working with.

(Why don't you give us the URL to the test site which demonstrates the problem too so that we can try it out with our own browsers.)

Posted: Sun Sep 16, 2007 4:23 pm
by s.dot
This sometimes happens to me if the page doesn't fully load when I call the javascripts. Thus elements don't exist yet.

Posted: Sun Sep 16, 2007 4:28 pm
by superdezign
scottayy wrote:This sometimes happens to me if the page doesn't fully load when I call the javascripts. Thus elements don't exist yet.
That's why it's recommended to put your JavaScript right before the closing <body> tag. Especially since if you assign the script to run onLoad, you still have to load the script before the page, thus slowing the load.

Posted: Sun Sep 16, 2007 4:31 pm
by s.dot
superdezign wrote:
scottayy wrote:This sometimes happens to me if the page doesn't fully load when I call the javascripts. Thus elements don't exist yet.
That's why it's recommended to put your JavaScript right before the closing <body> tag. Especially since if you assign the script to run onLoad, you still have to load the script before the page, thus slowing the load.
Mhm. I read a yahoo developer blog about this and have been doing it that way ever since. Don't know why I didn't do it from the beginning actually.. it only makes sense.

Posted: Mon Sep 17, 2007 6:16 am
by enchance
Still have the URL to that blog? I'd like to read it and see what other things he has to say about it.

Posted: Mon Sep 17, 2007 8:03 am
by The Phoenix
superdezign wrote:That's why it's recommended to put your JavaScript right before the closing <body> tag. Especially since if you assign the script to run onLoad, you still have to load the script before the page, thus slowing the load.
http://developer.yahoo.com/performance/ ... #js_bottom