FW: Don't click on the blue 'e'...

Well, here's an interesting bit of news in response to my plea for help locally from a coworker who is a web developer. Any clues on where to go to remove this offending bit of code as a test, or reasons it should be there? Brandon: does this ring any bells? brain[sic] -----Original Message----- ... I know of no clever IE debugging techniques. In my experience, however, IE's crashes normally occur when loading embedded objects like applets, Flash, SVG, fonts, etc, or when people do some unorthodox trickery in CSS or scripting. So when troubleshooting problems like this, my instinct is to dig through the source to see if there's anything odd going on. (Having validating markup and CSS helps this process.) My first observation is that the page is written in XHTML, and IE doesn't support XHTML[1]. This isn't normally a problem, necessarily, if the page is delivered as text/html (as these pages are), because IE will look at it and treat it as HTML "tag soup", and ignore the non-HTML XHTML stuff as bad markup to work around. However, the site is also emitting an <?xml ... ?> prolog at the start of the page. This has traditionally caused problems with IE in my experience, because IE isn't sure if it should look at it as a raw XML document or HTML. This issue is compounded by the fact that the page isn't well-formed XML at all. (There are HTML-style <BR> tags in there, for example.)