Stack Overflow In Line 0 - Anybody know what this is please?

Just had this appear up on my screen:-

[TSM]

ooo a vi****e problem

its realy easy to fix, just downgrade to XP

aparently its a javascript problem when browsing

[Paul the 6th]

hmmm, I switched to firefox a while back - top browser! and yeah, vista is rubbish so get xp pro!

Avoiding the carp posted above about multiple OS' & getting back to the OP...

The error is a well known javascript bug in the Vista version of Internet Explorer.

Change your browser, and the issue goes away. I'd reccomend either FireFox or Chrome.

[flymo]

I've debugged a number of sites with this error message before, always different reasons and never specifically down to IE in my experience.

Two common faults were down to the presence of the CA security suite, another was a script bug on the web server and a further couple were down to a third party pop-up blocker bug. In all cases removing or fixing the bug resolved the problem.

Originally Posted by flymo

Two common faults were down to the presence of the CA security suite, another was a script bug on the web server and a further couple were down to a third party pop-up blocker bug. In all cases removing or fixing the bug resolved the problem.

Granted, but I'm working on the assumption that the OP doesn't have priviledges to change the JS code on the server. Of course, that's a large assumption as the screenshot doesn't detail the server.

Therefore, using a different (and IMO better) browser is another resolution to the issue. Specifically in the case of Chrome, where JS code is optimised into machine code & cached before execution, this issue should never be present (if it is, the sandboxing of threads would rule out any negative effects other than a popup).

[fizzwheel]

Lets try and keep this on topic and knock it off with the digs about txt speak its not helpful and anything useful in this thread is just going to get lost.

Ta

[flymo]

Originally Posted by Baph

Granted, but I'm working on the assumption that the OP doesn't have priviledges to change the JS code on the server. Of course, that's a large assumption as the screenshot doesn't detail the server.

Therefore, using a different (and IMO better) browser is another resolution to the issue. Specifically in the case of Chrome, where JS code is optimised into machine code & cached before execution, this issue should never be present (if it is, the sandboxing of threads would rule out any negative effects other than a popup).

I'm not arguing with you Baph, particularly on the ins and outs of which browser feature is better for each etc but from experience I've learnt that there are often many different causes to problems. Just because one browser is affected and works in a particular way does not mean that its the browser at fault.

If somebody codes a site and does not thoroughly test it against IE, Firefox and any other popularly used browser then that surely is down to the site developer?

I've seen faults with IE, Firefox and even Chrome today during internal site testing so none of them are perfect.

To bring this back to the original question my comments relevance was only that moving to Firefox may hide the issue causing IE to error but it doesnt necessarily fix it.

Originally Posted by flymo

...sutff...

I agree completely, just that from a home user perspective, generally you can't edit the websites you visit. So you can get around sloppy code by changing the browser usually.

T'is a workaround, not a fix.

SV-net, any joy yet?