yeah, I've not tested it here, but I've noticed on my forums that it now happens to seamonkey too (the old 'mozilla' - and therefore, also gecko based) - it used to always happen on konqueror (and still does) but I'm sure it's a new thing on firefox...
They must have changed their javascript parsing somehow, but I've not bothered looking at it yet.
I remember, konqueror claimed maximum ECMA compatibility around the time when it happened there, but not on firefox.. Maybe firefox has been 'fixed' causing this to now happen.. presumably needs a javascript fix.
Or, I'm talking rubbish. You decide!
____________________________
#f3i2g#
Disclaimer: I'm Welsh, left-handed, and stupid.
#f3i2g#
[Last edited by jamie at 08-11-2007 12:17 AM]