| Author |
Message |
|
Mythra
#1 / 15
|
 Bug In IExplorer I am pretty sure that this is a bug and not place by design (it must be a feature!!!). I wrote a script (error catching script) and made it a custom error script
in IIS. I then wrote another script that would open a modal dialog window
using Window.showModalDialog. Then I wrote one more script that had an
error, (ASP error, serverside script), in it. On the custom error page, I
made a link/button that when it was clicked, it would refresh the page.
Now, when the page is ran and the dialog is open, the error is hit so the
server would redirect to the custom error page. If I click on Refresh (the
button i made), IExplorer would get stuck in an infinite loop and I would
have to kill it in order to release the CPU it was taking up (99%).
Bug?
Mythran
|
| Sun, 14 Nov 2004 04:14:51 GMT |
|
 |
|
Ray at wor
#2 / 15
|
Bug In IExplorer I didn't really follow exactly what you're saying here, but infinite loops are caused (usually) by faulty logic or coding. The server is just doing what you instructed it to do. Ray at work
Quote: > I am pretty sure that this is a bug and not place by design (it must be a > feature!!!). > I wrote a script (error catching script) and made it a custom error script
> in IIS. I then wrote another script that would open a modal dialog window
> using Window.showModalDialog. Then I wrote one more script that had an
> error, (ASP error, serverside script), in it. On the custom error page, I
> made a link/button that when it was clicked, it would refresh the page.
> Now, when the page is ran and the dialog is open, the error is hit so the
> server would redirect to the custom error page. If I click on Refresh
(the
> button i made), IExplorer would get stuck in an infinite loop and I would
> have to kill it in order to release the CPU it was taking up (99%).
> Bug?
> Mythran
|
| Sun, 14 Nov 2004 04:30:30 GMT |
|
|
|
Mythra
#3 / 15
|
Bug In IExplorer No...the logic is NOT the problem (well, besides the error). Try it for yourself and you will see what I mean. Mythran
|
| Sun, 14 Nov 2004 04:58:55 GMT |
|
|
|
MV
#4 / 15
|
Bug In IExplorer With that kind of behavior, it doesn't matter whether there is a logic problem or not I think - that would qualify as a bug since it could be used abusively. What version of IE was this, and would you mind posting code to make it easy to
replicate?
Quote: > No...the logic is NOT the problem (well, besides the error). Try it for > yourself and you will see what I mean. > Mythran
|
| Sun, 14 Nov 2004 06:10:45 GMT |
|
|
|
Mythra
#5 / 15
|
Bug In IExplorer Quote: > What version of IE was this, and would you mind posting code to make it
easy to
> replicate?
I am using Internet Explorer 5.5sp2 Q319182; Q321232; Ok, here is the code I am using.
Make the following line the first line of your custom asp 500-100 error
page. Please note: You must have a custom 500-100 error page to get this to
work as the normal error page does not have a refresh link/button and you
can't right-click a modal page (without modifications).
<a href="javascript:location.reload();">Refresh Page</a>
Now, create the following two pages...
Main.asp:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>Main Test Page</title>
<script language="VBScript">
Sub cmdCrashExplorer_OnClick()
Window.showModalDialog "PageWithError.asp"
End Sub
</script>
</head>
<body>
<input type="button" name="cmdCrashExplorer" value="Crash Explorer">
</body>
</html>
Now the second page...
PageWithError.asp
<%
Option Explicit
A = 1
%>
Now, when you click on the cmdCrashExplorer button, the modal window will
open correctly, but with your custom error page (if you set that up
already). If you click the refresh link that I have stated to put into the
page, Internet explorer (and maybe windows for < NT machines) will lock up
completely.
Since I have Windows 2k, I got out of it by just killing IE, but I don't
know if Win98 will let you do that since it may lock up the entire system.
Anywho, let me know who, what, when, where, and why this is happening....and
if a fix is already out for it...
Mythran
|
| Sun, 14 Nov 2004 07:18:38 GMT |
|
|
|
Mythra
#6 / 15
|
Bug In IExplorer Oops, one more thing...I have not checked to see if it times out after a certain period of time...as more than 10 seconds is too long for any program to not respond at all (even close message to the server). Mythran
Quote: > With that kind of behavior, it doesn't matter whether there is a logic problem > or not I think - that would qualify as a bug since it could be used abusively. > What version of IE was this, and would you mind posting code to make it
easy to
> replicate?
> > No...the logic is NOT the problem (well, besides the error). Try it for
> > yourself and you will see what I mean.
> > Mythran
|
| Sun, 14 Nov 2004 07:20:04 GMT |
|
|
|
Gurge
#7 / 15
|
Bug In IExplorer Interesting.... First, the 500-100 page has built-in refresh link. It appears that all modal window links are opened in a new window (check your taskbar then click on refresh). I guess IE is getting confused when trying to open "javascript:location.reload();" or "javascript:window.location=window.location;" in a new window. --
Gurgen Alaverdian
http://www.gurgensvbstuff.com
Quote: > > What version of IE was this, and would you mind posting code to make it > easy to > > replicate? > I am using Internet Explorer 5.5sp2 Q319182; Q321232; > Ok, here is the code I am using.
> Make the following line the first line of your custom asp 500-100 error
> page. Please note: You must have a custom 500-100 error page to get this
to
> work as the normal error page does not have a refresh link/button and you
> can't right-click a modal page (without modifications).
> <a href="javascript:location.reload();">Refresh Page</a>
> Now, create the following two pages...
> Main.asp:
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
> <html>
> <head>
|
| Sun, 14 Nov 2004 08:27:23 GMT |
|
|
|
Gurge
#8 / 15
|
Bug In IExplorer This can also be simulated: Just add this to any page: <a href="javascript:location.reload()" target="_blank"> This will freeze IE 5.5 and Netscape 6.2.
Netscape 4.7 seems handles this by throwing an error.
--
Gurgen Alaverdian
http://www.gurgensvbstuff.com
Quote: > Interesting.... First, the 500-100 page has built-in refresh link.
Opps ... You did mentioned that though.... It
Quote: > appears that all modal window links are opened in a new window (check your > taskbar then click on refresh). I guess IE is getting confused when trying > to open "javascript:location.reload();" or > "javascript:window.location=window.location;" in a new window. > --
> Gurgen Alaverdian
> http://www.gurgensvbstuff.com
> > > What version of IE was this, and would you mind posting code to make
it
> > easy to
> > > replicate?
> > I am using Internet Explorer 5.5sp2 Q319182; Q321232;
> > Ok, here is the code I am using.
> > Make the following line the first line of your custom asp 500-100 error
> > page. Please note: You must have a custom 500-100 error page to get
this
> to
> > work as the normal error page does not have a refresh link/button and
you
> > can't right-click a modal page (without modifications).
> > <a href="javascript:location.reload();">Refresh Page</a>
> > Now, create the following two pages...
> > Main.asp:
> > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
> > <html>
> > <head>
|
| Sun, 14 Nov 2004 08:48:08 GMT |
|
|
|
MV
#9 / 15
|
Bug In IExplorer Oh, yeah. IE6, WinXP, it just hangs the CPU. Had to kill IE.
Quote: > This can also be simulated: > Just add this to any page: > <a href="javascript:location.reload()" target="_blank"> > This will freeze IE 5.5 and Netscape 6.2.
> Netscape 4.7 seems handles this by throwing an error.
> --
> Gurgen Alaverdian
> http://www.gurgensvbstuff.com
> > Interesting.... First, the 500-100 page has built-in refresh link.
> Opps ... You did mentioned that though....
> It
> > appears that all modal window links are opened in a new window (check your
> > taskbar then click on refresh). I guess IE is getting confused when
> trying
> > to open "javascript:location.reload();" or
> > "javascript:window.location=window.location;" in a new window.
> > --
> > Gurgen Alaverdian
> > http://www.gurgensvbstuff.com
> > > > What version of IE was this, and would you mind posting code to make
> it
> > > easy to
> > > > replicate?
> > > I am using Internet Explorer 5.5sp2 Q319182; Q321232;
> > > Ok, here is the code I am using.
> > > Make the following line the first line of your custom asp 500-100 error
> > > page. Please note: You must have a custom 500-100 error page to get
> this
> > to
> > > work as the normal error page does not have a refresh link/button and
> you
> > > can't right-click a modal page (without modifications).
> > > <a href="javascript:location.reload();">Refresh Page</a>
> > > Now, create the following two pages...
> > > Main.asp:
> > > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
> > > <html>
> > > <head>
|
| Sun, 14 Nov 2004 09:09:36 GMT |
|
|
|
Mythra
#10 / 15
|
Bug In IExplorer You mean I actually found a bug in Microsoft and identified it correctly?!? A FEATURE!!! Anywho, I would like to thank my mother, father, ... Heh...jk...anywho...who do we talk with associated with Microsoft to get
this fixed (with my name on a plaque high in the air...)
No I am not egotistical or a snot....I am just happy that I have found a bug
and that I could help Msoft by pointing it out.....
Boo...
Mythran
|
| Sun, 14 Nov 2004 13:39:10 GMT |
|
|
|
Mythra
#11 / 15
|
Bug In IExplorer I retried this bug on my work machine again, and only the one new IE screen froze....but in order to kill it, I had to kill IE... Mythran
|
| Sun, 14 Nov 2004 13:40:44 GMT |
|
|
|
MVP
#12 / 15
|
Bug In IExplorer
:: You mean I actually found a bug in Microsoft and identified it :: correctly?!? A FEATURE!!! Anywho, I would like to thank my mother, :: father, ... :: :: Heh...jk...anywho...who do we talk with associated with Microsoft to :: get this fixed (with my name on a plaque high in the air...) :: :: No I am not egotistical or a snot....I am just happy that I have :: found a bug and that I could help Msoft by pointing it out..... :: Microsoft Product Support Services Feedback
http://support.microsoft.com/support/feedback/
is available to anyone to submit a bug report...
In reality, the bug you found is a lot easier to reproduce...
===page1.htm===
<html>
<body>
<input type="button"
onclick="window.showModalDialog('page2.htm');"
value="showModalDialog">
</body>
</html>
===page2.htm===
<html>
<body>
<a href="javascript:location.reload()">Reload Page</a><br>
</body>
</html>
--
Michael Harris
Microsoft.MVP.Scripting
Seattle WA US
--
|
| Mon, 15 Nov 2004 08:18:06 GMT |
|
|
|
MVP
#13 / 15
|
Bug In IExplorer
:: You mean I actually found a bug in Microsoft and identified it :: correctly?!? A FEATURE!!! Anywho, I would like to thank my mother, :: father, ... :: :: Heh...jk...anywho...who do we talk with associated with Microsoft to :: get this fixed (with my name on a plaque high in the air...) :: :: No I am not egotistical or a snot....I am just happy that I have :: found a bug and that I could help Msoft by pointing it out..... :: :: Microsoft Product Support Services Feedback
http://support.microsoft.com/support/feedback/
is available to anyone to submit a bug report...
In reality, the bug you found is a lot easier to reproduce...
===page1.htm===
<html>
<body>
<input type="button"
onclick="window.showModalDialog('page2.htm');"
value="showModalDialog">
</body>
</html>
===page2.htm===
<html>
<body>
<a href="javascript:location.reload()">Reload Page</a><br>
</body>
</html>
--
Michael Harris
Microsoft.MVP.Scripting
Seattle WA US
--
|
| Mon, 15 Nov 2004 09:05:53 GMT |
|
|
|
Mythra
#14 / 15
|
Bug In IExplorer Thanks...umm....doing that will create an infinite loop....well..it can be stopped using the stop button...but dialog boxes don't have that....that is why I placed a command button instead :) Mythran
===page1.htm===
<html>
<body>
<input type="button"
onclick="window.showModalDialog('page2.htm');"
value="showModalDialog">
</body>
</html>
===page2.htm===
<html>
<body>
<a href="javascript:location.reload()">Reload Page</a><br>
</body>
</html>
--
|
| Mon, 15 Nov 2004 10:51:22 GMT |
|
|
|
Mythra
#15 / 15
|
Bug In IExplorer Sorry, read your last post wrong Michael. I, for some unknown ordinal reason, thought that yer href was instead the body tag and it was an onload event... In reality, you did not create an infinite loop after all...my mistake!
Mythran
|
| Tue, 16 Nov 2004 00:54:45 GMT |
|
| |
