D
David Mark
http://groups.google.com/group/jquery-dev/browse_thread/thread/5f8cade148bdafa5
"I debugged a tricky problem today in an app that came down to jQuery
hanging IE."
I am sorry to hear _that_. I'd be glad to help you with this
problem.
"I know v1.1.2 is ancient, but I am trying to understand the root
cause, so I'm just curious if anyone else has seen anything like this.
Just trying to gather info."
Now, what sort of irresponsible space-case would use jQuery 1.1x?
Perhaps they are unable to upgrade due to broken compatibility? That
rings a bell.
"The problem:"
_A_ problem.
"On one page in a webapp, the content is fully delivered but IE
continues showing the "spinner" and "Waiting for ..." appears in the
status bar. jQuery's ready() event doesn't fire and IE just hangs in
that state."
Wonderful! Sorry, I meant that's a shame.
"Here is the info:
1) jQuery 1.1.2, IE7 on a dual-core HP laptop"
There it is. See above.
"2) Problem only happens in above configuration, and even then it is
"random". When BIOS is changed to disable dual-core, problem
disappears"
In fifteen years, I've never encountered such a thing. Of course, I
don't rely on fossilized code monkey droppings either.
"3) When the IE "hack" to detect domcontentloaded is removed from the
jQuery source (and window.onload is used instead), the problem
disappears"
Told you so (repeatedly). But perhaps I don't understand what
"programmers" _really_ need from an API.
"Apparently, the hack of inserting the <script defer=true src=//:> tag
is what causes the browser to go into the hung state. I'm not really
sure what IE does internally when this kind of tag is inserted, but
somehow it is triggering a problem."
Curiouser and curiouser.
"I suspect that there is an underlying problem with IE or perhaps the
drivers, or perhaps the hardware or something, and jQuery is just
exposing the underlying problem."
Hacks are good for that. What made you think this one would work
reliably? Because it is in jQuery?
And if there is one event you don't want to blow, it's load. It's
not as if this hack is going to make your app "load faster".
"So, if anyone has ever seen a problem like this, please let me know
so I can try to get a little more info. Thanks!"
Who cares if anyone (else) has seen it? Programming by collaborative
misunderstanding is what led to this. There are three solutions:-
1. Stop using jQuery
2. Create your own patched jQuery (and hope this was an isolated screw-
up).
Of course, we know there is far more wrong with jQuery (particularly
the older versions) than this one line deferred script hack. Seems
like a major waste of time to monkey around with the thing every time
a new bug is reported. And even if upgrading were possible, it
wouldn't help this issue as that hack is still present (and in the
other "majors" as well). Good luck!
This adjacent post is an illuminating look into the jQuery design/
development process:-
http://groups.google.com/group/jquery-dev/t/f8f2906be4d4491
Things can only get better from here.
As for the community efforts:-
http://groups.google.com/group/jquery-dev/t/25652ea60a4f5db2
"I got bit by a number of bugs in the Color Animations plugin. So, I
fixed them and uploaded the fix to the comments on the issue I
submitted against it.
Then I noticed, other people have submitted patches as far back as
almost 2 years ago. So it looks like this module is no longer being
actively maintained."
And the 2009 Summit on Attributes and Heights is still ongoing. No
consensus yet.
http://groups.google.com/group/jquery-dev/t/baef5e91bd714033
"I debugged a tricky problem today in an app that came down to jQuery
hanging IE."
I am sorry to hear _that_. I'd be glad to help you with this
problem.
"I know v1.1.2 is ancient, but I am trying to understand the root
cause, so I'm just curious if anyone else has seen anything like this.
Just trying to gather info."
Now, what sort of irresponsible space-case would use jQuery 1.1x?
Perhaps they are unable to upgrade due to broken compatibility? That
rings a bell.
"The problem:"
_A_ problem.
"On one page in a webapp, the content is fully delivered but IE
continues showing the "spinner" and "Waiting for ..." appears in the
status bar. jQuery's ready() event doesn't fire and IE just hangs in
that state."
Wonderful! Sorry, I meant that's a shame.
"Here is the info:
1) jQuery 1.1.2, IE7 on a dual-core HP laptop"
There it is. See above.
"2) Problem only happens in above configuration, and even then it is
"random". When BIOS is changed to disable dual-core, problem
disappears"
In fifteen years, I've never encountered such a thing. Of course, I
don't rely on fossilized code monkey droppings either.
"3) When the IE "hack" to detect domcontentloaded is removed from the
jQuery source (and window.onload is used instead), the problem
disappears"
Told you so (repeatedly). But perhaps I don't understand what
"programmers" _really_ need from an API.
"Apparently, the hack of inserting the <script defer=true src=//:> tag
is what causes the browser to go into the hung state. I'm not really
sure what IE does internally when this kind of tag is inserted, but
somehow it is triggering a problem."
Curiouser and curiouser.
"I suspect that there is an underlying problem with IE or perhaps the
drivers, or perhaps the hardware or something, and jQuery is just
exposing the underlying problem."
Hacks are good for that. What made you think this one would work
reliably? Because it is in jQuery?
And if there is one event you don't want to blow, it's load. It's
not as if this hack is going to make your app "load faster".
"So, if anyone has ever seen a problem like this, please let me know
so I can try to get a little more info. Thanks!"
Who cares if anyone (else) has seen it? Programming by collaborative
misunderstanding is what led to this. There are three solutions:-
1. Stop using jQuery
2. Create your own patched jQuery (and hope this was an isolated screw-
up).
Of course, we know there is far more wrong with jQuery (particularly
the older versions) than this one line deferred script hack. Seems
like a major waste of time to monkey around with the thing every time
a new bug is reported. And even if upgrading were possible, it
wouldn't help this issue as that hack is still present (and in the
other "majors" as well). Good luck!
This adjacent post is an illuminating look into the jQuery design/
development process:-
http://groups.google.com/group/jquery-dev/t/f8f2906be4d4491
Things can only get better from here.
As for the community efforts:-
http://groups.google.com/group/jquery-dev/t/25652ea60a4f5db2
"I got bit by a number of bugs in the Color Animations plugin. So, I
fixed them and uploaded the fix to the comments on the issue I
submitted against it.
Then I noticed, other people have submitted patches as far back as
almost 2 years ago. So it looks like this module is no longer being
actively maintained."
And the 2009 Summit on Attributes and Heights is still ongoing. No
consensus yet.
http://groups.google.com/group/jquery-dev/t/baef5e91bd714033