Discussion:
Is this an IE8 bug?
(too old to reply)
PA Bear [MS MVP]
2009-08-24 15:35:51 UTC
Permalink
See...

IE Developer Center
http://msdn.microsoft.com/en-us/ie/default.aspx

Learn IE8
http://msdn.microsoft.com/en-us/ie/aa740473.aspx

HTML and DHTML Overviews and Tutorials
http://msdn.microsoft.com/en-us/library/ms537623.aspx and

Cascading Style Sheets (CSS)
http://msdn2.microsoft.com/en-us/ie/aa740476.aspx

Or you could post here instead:

MSDN IE Development Forums
http://social.msdn.microsoft.com/forums/en-US/category/iedevelopment/

=> Those with IE7- and/or IE8-specific questions or comments can post to and
seek support in IE General newsgroup:
microsoft.public.internetexplorer.general

On the web:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.internetexplorer.general

In your newsreader:
news://msnews.microsoft.com/microsoft.public.internetexplorer.general
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Client - since 2002
www.banthecheck.com
Hello IE gurus,
Sorry for cross post because I can't figure
out which is the proper newsgroup
to post this question.
We have a piece of HTML that crashes IE8
developer tools. Just extract bug.html from
the attachment, open it with IE8 then press F12.
Wait several seconds, IE8 crashes.
While we can't figure out where the HTML problem
is, we have to consider it's a DOM parser bug
which creates cross-linked DOM elements that
results in the IE crash.
It seems not only IE8, IE6~8 DOM parsers are
affected by this bug, because we get same deadloop
while travelling DOM tree with javascript, something
like following snippet.
function fTraverseDOMTree(obj, level) {
if (obj != null) {
var i = 0;
var nextObj = obj.childNodes[i];
while (nextObj) {
fTraverseDOMTree(nextObj, level + 1);
i++;
nextObj = obj.childNodes[i];
}
}
}
1 Is there any problem in the attachment HTML?
2 Is it the IE bug?
Thanks.
best regards,
lu0
l***@community.nospam
2009-08-25 12:15:54 UTC
Permalink
PA Bear,

Thanks for the reply.
Anyway, key to solving the problem is not captured, I'll post question to
news://msnews.microsoft.com/microsoft.public.internetexplorer.general. :)
Post by PA Bear [MS MVP]
See...
IE Developer Center
http://msdn.microsoft.com/en-us/ie/default.aspx
Learn IE8
http://msdn.microsoft.com/en-us/ie/aa740473.aspx
HTML and DHTML Overviews and Tutorials
http://msdn.microsoft.com/en-us/library/ms537623.aspx and
Cascading Style Sheets (CSS)
http://msdn2.microsoft.com/en-us/ie/aa740476.aspx
MSDN IE Development Forums
http://social.msdn.microsoft.com/forums/en-US/category/iedevelopment/
=> Those with IE7- and/or IE8-specific questions or comments can post to
microsoft.public.internetexplorer.general
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.internetexplorer.general
news://msnews.microsoft.com/microsoft.public.internetexplorer.general
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Client - since 2002
www.banthecheck.com
Hello IE gurus,
Sorry for cross post because I can't figure
out which is the proper newsgroup
to post this question.
We have a piece of HTML that crashes IE8
developer tools. Just extract bug.html from
the attachment, open it with IE8 then press F12.
Wait several seconds, IE8 crashes.
While we can't figure out where the HTML problem
is, we have to consider it's a DOM parser bug
which creates cross-linked DOM elements that
results in the IE crash.
It seems not only IE8, IE6~8 DOM parsers are
affected by this bug, because we get same deadloop
while travelling DOM tree with javascript, something
like following snippet.
function fTraverseDOMTree(obj, level) {
if (obj != null) {
var i = 0;
var nextObj = obj.childNodes[i];
while (nextObj) {
fTraverseDOMTree(nextObj, level + 1);
i++;
nextObj = obj.childNodes[i];
}
}
}
1 Is there any problem in the attachment HTML?
2 Is it the IE bug?
Thanks.
best regards,
lu0
Loading...