Well, I've been doing all that, and it doesn't seem that any Javascript errors are triggering the crashes; very few of the XWiki pages elicit errors of that sort from IE. I'm going to leave it on anyway, in case they're cumulatively leading to some memory or stack corruption that is later triggered by some otherwise harmless event. But it occurs to me that if you've beaten XWiki against IE6 for a while, you may have some clues about what kinds of things tip its equilibrium? I'm grasping at straws here, as you can imagine. The perverse irony of this situation is that the flaws of one Microsoft product may prompt ditching XWiki in favor of another Redmond tar-baby: SharePoint Server. brain[sic]
-----Original Message----- From: THOMAS, BRIAN M (SBCSI) Sent: Wednesday, November 01, 2006 1:03 PM To: [email protected] Subject: RE: [xwiki-users] IE browser crash
Brandon:
Thanks for a quick response. I should have specified that it was IE6 (I had all but forgotten that there was any other version).
And ditto on Firefox, though I use FireBug (and anything else I can get my hands on - hadn't heard of "Web Developer"). After becoming used to that, using IE is like working blindfolded, handcuffed, with thick gloves on... in a sewer.
Your concern about sounding patronizing notwithstanding, you managed to mention one thing I overlooked (looking at the error icon, duh) and one thing of which I was unaware (option for notification on script errors) as well one thing I've only just begun asking the users to do (sending me the messages that Windows offers to send when tattling on a misbehaving program).
Not bad on little to no evidence... if you're not careful, you might encourage more of such questions in the future, to the everlasting chagrin of all the regulars. I now submit to the discipline of the group.
However, it's hard to imagine any (lawful) punishment that would deter me from seeking help for a problem of this urgency, so perhaps you are the one who should be punished...
brain[sic]