We have a nifty little web app that we've whipped up. The client-side is almost entirely jQuery, which supports IE9 (as well as other versions). Preliminary browser testing has come back very positive, with one exception.
We have a Project Manager who is experiencing some crazy things on his instance of IE9. All of our testers, analysts and developers have tested the same pages as this PM with IE9 on their machines and the web app works/displays perfectly fine. It's just this one individuals machine where the following things are happening:
- "Internet Explorer cannot display the webpage" errors on ~80% of pages/page loads
- Image files (that we store on Akamai CDN) are not downloaded and show up as broken images (red X's)
I already had him check to see if the
Use proxy server for your LAN was unchecked (and it is) - I've read that when this option is checked it can cause similar issues.
I have no aversion to rolling up my sleeves and debugging the web app with F12 Developer Tools while working at his machine, but this just doesn't feel like a "code issue" seeing that it works on everyone else's IE9 instance (typical developer - "Couldn't be my code!!!").
This is holding up our release because the PM ultimately has to sign off on the QA testing - and he's not about to do it when he can't even verify the app works for himself!
Are there configuration or properties files that IE9 uses that are defining things incorrectly in his instance?
What would a pro webmaster do? Thanks in advance!