Boy, how bad bad bad Internet Explorer is...
Julian Buss, May 26th, 2009 16:17:39
We developed a cool web application using XPages for a customer.
It has been tested with:
- Firefox 3.x
- Internet Explorer 8 in IE 7 compatibility mode
- Internet Explorer 7 on Windows Vista
- Internet Explorer 7 on Terminal Server WIndows Server 2008
- Internet Explorer 7 on Windows XP SP2
and runs fine in all these configurations.
Now I get a support call from the customer that one of their customers has problems with Internet Explorer 7 (partial updates do now work and some dojo error messages).
Can you believe that?!? Why does it work in one IE 7 and not in the other? And I'm not able to reproduce it here, since it works on all my test machines.
As much fun web development is with XPages now, it's still a damn pain to support Microsoft Internet Explorer.
Know what? I really wonder how the developers of the Microsoft web sites and applications can stand that. How do they survive developing primary for Internet Explorer?
Why, good god please tell me why is a company like Microsoft with brazillions of developers not able to create a decent, working and modern browser? It. is. such. a. shame.
Update 1: I got the error message on the problematic machine: "XSP is null or not an object". Same is described here, but in that case it had something to do with using Domino and IIS. My customer runs on Linux.
And it is not caused by Internet Explorer security settings - we tried many combinations without luck.