This is odd!



  • Just wondering the halls of /. and followed the story of Top 10 List of Worldwide Internet Censors .

     

    Finished reading the site, clicked back to go back to slashdot and then this....

     Screen grab

    <a href="http://img228.imageshack.us/my.php?image=grab1mg4.jpg" target="_blank"><img src="http://img228.imageshack.us/img228/1876/grab1mg4.th.jpg" border="0" alt="Free Image Hosting at www.ImageShack.us" /></a>

     All working fine now!!!



  • The real WTF is that you're using Internet Explorer.



  • [quote user="Laertes"]The real WTF is that you're using Internet Explorer.
    [/quote]

     At work I'm afraid!! - the company I work for use an online customer care tool that only really works in IE!!! - I would love to look at that code!!!

     



  • @Laertes said:

    The real WTF is that you're using Internet Explorer.

    And Norton (IIRC), and Quicktime, and Outlook..... ;)



  • [quote user="nuclear_eclipse"][quote user="Laertes"]The real WTF is that you're using Internet Explorer.
    [/quote] And Norton (IIRC), and Quicktime, and Outlook..... ;)[/quote]

     

    10 points to the first person to say.... "..and windows...." ;)



  • ... and Windows.



  • [quote user="Laertes"]... and Windows.
    [/quote]

     

    Sorry, but your failed...  There was no capital W in my post :p

    (Good god man, how old are you </talking to himself>)



  • Am I the only one who's noticed an email message with the subject - "Fires Download".

    That was very strange. Hope it wasn't his boss.



  • [quote user="Laertes"]The real WTF is that you're using Internet Explorer.
    [/quote]

    Can we stop saying that?  It's most unhelpful.

    Meanwhile, stack overflows in the browser usually indicate scripting that has somehow become recursive (which would happen on ANY browser).



  • ..and windows....



  • [quote user="mrprogguy"]Meanwhile, stack overflows in the browser usually indicate scripting that has somehow become recursive (which would happen on ANY browser).[/quote]

    Only a shitty scripting engine would cause a stack overflow just from interpreting a script with too much recursion. Firefox, for example, stops executing the script and displays a "too much recursion" message box.

    The real WTF is defending Internet Explorer.



  • [quote user="HeroreV"]

    [quote user="mrprogguy"]Meanwhile, stack overflows in the browser usually indicate scripting that has somehow become recursive (which would happen on ANY browser).[/quote]

    Only a shitty scripting engine would cause a stack overflow just from interpreting a script with too much recursion. Firefox, for example, stops executing the script and displays a "too much recursion" message box.

    The real WTF is defending Internet Explorer.

    [/quote]

    Agreed. 



  • And stopping with a 'too much recursion' dialog instead of a 'stack overflow' one is so much better ... how exactly?



  • Too much recursion is too much recursion.

    You can't let the browser go on forever.
     

    The stack overflow is an error in IE itself.

    Providing the message "Too much recursion" keeps control in the browser's hands and provides a proper, usable error message.

    It's the difference between
    driving into a wall -- and stopping
    auto-break before the wall -- and stopping
     



  • [quote user="dhromed"]The stack overflow is an error in IE itself.[/quote]

    No, it's an error in the JScript execution which IE catches and shows in a message box. You can keep using IE after such a message, and JScript will work fine on the next page. It's just a slightly different error message to the one FF chooses.

    There are many places to bash IE but this isn't one of them.
     



  • [quote user="HeroreV"]

    [quote user="mrprogguy"]Meanwhile, stack overflows in the browser usually indicate scripting that has somehow become recursive (which would happen on ANY browser).[/quote]

    Only a shitty scripting engine would cause a stack overflow just from interpreting a script with too much recursion. Firefox, for example, stops executing the script and displays a "too much recursion" message box.

    The real WTF is defending Internet Explorer.

    [/quote]

    Odd... when I go to a page in IE that has an out of control script, it pops up a little message box that says something to the effect that the page has shitty javascript that's making the browser unstable, do I want to stop running it.

     



  • [quote user="Bob Janova"]

    [quote user="dhromed"]The stack overflow is an error in IE itself.[/quote]

    No, it's an error in the JScript execution which IE catches and shows in a message box. You can keep using IE after such a message, and JScript will work fine on the next page. It's just a slightly different error message to the one FF chooses.

    There are many places to bash IE but this isn't one of them.
    [/quote]

    "Stack Overflow" as displayed by IE is not a normal runtime/interpret-time error nicely caught and controlled by IE's JS engine, but a screwup in the engine itself -- the fact that it's the fucked script causes an excessive amount of recursion is irrelevant in this issue. What's relevant is how the JScript engine handles it.

    I consider the engine part of IE. Maybe that's personal, but I think that makes sense.

    One can keep on using IE. That means the error is non-fatal. Nonetheless, it is an error in IE. One can get non-fatal errors in any program. Photoshop sometimes says "Could not complete operation because of a program error", and yet happily continues running. This is nice, because instead of killing PS, I get a chance to save my lovely design and relaunch PS.

    [quote user="webzter"]Odd...
    when I go to a page in IE that has an out of control script, it pops up
    a little message box that says something to the effect that the page
    has shitty javascript that's making the browser unstable, do I want to
    stop running it.[/quote]

    Depends on the speed.

    Slow scripts provide
    the message that it's running slow and do you want to stop it?, but if IE's JS engine runs out of stack space before that time, it'll bomb.


Log in to reply
 

Looks like your connection to What the Daily WTF? was lost, please wait while we try to reconnect.