|
Boy, how bad bad bad Internet Explorer is...
Julian Buss, May 26th, 2009 16:17:39
Tags: XPages
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.
Comments (16) | Permanent Link
1) Boy, how bad bad bad Internet Explorer is...
check the settings for internet temporary files and make sure the radio button for new file check is not set to automatic. 2) Boy, how bad bad bad Internet Explorer is...
thanks nelson, but it is on "automatic". I tried other settings - no difference. It seems that the IE cannot load the dojo JS files.. 3) Boy, how bad bad bad Internet Explorer is...
Automatic means Microsoft makes its best guess to determine if a page needs to be fetched from cache vs. anew. What I meant to say is - set this setting to "every visit to the page". At least, when we wrote ajax apps, having it set to automatic made our web 2.0 apps act "weird" 4) Boy, how bad bad bad Internet Explorer is...
I tried "every visit to the page" - no luck, either. 5) Boy, how bad bad bad Internet Explorer is...
IE costs customers a lot of money in web development. I think there would be more backlash on MS if more companies knew how horrible the browser is. Good article: { Link } 6) Boy, how bad bad bad Internet Explorer is...
Could it be something simple like a security preference that disables javascript ? Of course another possibility is a 'browser helper object', some rouge toolbar that has a script blocker in it or even a virus BHO. 7) Boy, how bad bad bad Internet Explorer is...
Declan, unfortunately not, there is no simple solution. We tested all security settings - no luck. I disabled all add ons (there was an antivirus adddon) - no luck. Virus is unlikely, since the machine is in a corporate environment with professinal antivirus in place. In the company we found another machine which has the same OS and IE version, but on which it works. The customer tries to nail down the differences between the both machines. 8) Boy, how bad bad bad Internet Explorer is...
IE7 on XP and IE7 on Vista are a slight different. See blog { Link } 9) Boy, how bad bad bad Internet Explorer is...
Frank, thanks for the link - we already tested on XP and Vista, without difference - runs on both at our site. 10) Boy, how bad bad bad Internet Explorer is...
let the IE6/7/8 deathmarch begin! 11) Boy, how bad bad bad Internet Explorer is...
We are also facing that issue with partial updates not working on IE7 (sometimes). It seems that the information which part should be updated is not calculated ($$xspsubmitid is null or not an object). 12) Boy, how bad bad bad Internet Explorer is...
Dennis, but does it work on one IE on one machine fine and not at all on another? 13) Boy, how bad bad bad Internet Explorer is...
Microsoft are a huge company.. and you would be right to think they would have "brazillions" of developers. But I met someone recently who worked in Microsoft and said that of the 80,000 employees, less than 750 produce software. Considering the huge range of s/w they produce, this means there aren't alot of coders producing product. But they may have tonnes of support people. But having said that, they may not need so many support people if they properly write and test applications in the first place... 14) Boy, how bad bad bad Internet Explorer is...
Julian, I can reproduce it on other workstations, too. Time to do some more debugging... :( 15) Boy, how bad bad bad Internet Explorer is...
Hi! I know it's been a year since you guys discussed this, but I've now stumbled upon a problem that seems to be related to this posting. In IE7, I get the error "'document.forms[...].$$xspsubmitid' is null or not an object" when I try to save the changes in a Notes Document from web, while the page is working just fine in Firefox. Further details are provided at { Link } ! Any help is greatly appreciated! Thank you! 16) Boy, how bad bad bad Internet Explorer is...
question is: which Domino version do you use? If 8.5.0, that that's the problem -> upgrade to 8.5.1. |
