Issues using IE10 or IE11 with Cold Fusion 11

[userCold9]

Hi,

Some users of the application are using IE 10 or IE 11 and is working file.

Some users of the application using IE 10 or IE 11 the application is not working.

Running Cold Fusion 11 with Update 3 and IIS 7. The servers are Windows 2008, 32 bit.

Does anyone have any ideas?

Thanks,

Mike

[WolfShade]

Have you tested with FireFox and/or Chrome?

CF Server only generates HTML on-the-fly based upon instructions from the CF developer.  It's the same HTML for every browser. 

If there are some that have issues, and some that do not, then the issue is most likely browser settings or network security settings.

You don't mention if the users who report good and bad experiences are on the same network.  If it's a public-facing site and the users are all from different networks, then the issue is _very_ likely not CF Server.

Just my two cents.

V/r,

^_^

[userCold9]

The users go thry a portal to access the appliction.

Should there be somthing like: <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE10" /> on every page?

I can access the site using FireFox.The site does not work with Chrome.

The site has no issues with IE 8 or 9.

Thanks,

Mike

[WolfShade]

Well, it would be best if every page had it so that every page would be forced to IE10 compatibility; but I suppose you _could_ use it only on the pages that are experiencing issues.  I'm one for consistency, though.

HTH,

^_^

[Carl Von Stetten]

What does "the application is not working" mean, specifically?  Are you getting errors?  Are you getting different display results?

[userCold9]

In one area of the application uses CFlayout, CFlayoutarea, CFajaximport for producing tabs across the top of the page.

Some individuals can see the tabs and others cannot.

Thanks,

Mike

[Carl Von Stetten]

Keep in mind that those features (CFLayout, CFLayoutArea) are based on the ExtJS library, and the version of the library embedded in ColdFusion is way out of date.  There are probably going to be issues with browsers that are applying more modern CSS/HTML5 standards (like Chrome and possibly newer releases of IE 10/11 patched by Windows Update).  Have you compared the IE build numbers between machines that "work" and those that don't?

Also bear in mind that Microsoft has dropped support for IE 10 as of 1/12/16 (see https://support.microsoft.com/en-us/lifecycle#gp/Microsoft-Internet-Explorer), so unless you are running Windows Vista, you should upgrade all computers to IE 11.

[userCold9]

Hi,

It seems that individuals are using IE 11 and in production one section is not working properly.

But in the Test and Training environment, the same code is working just fine.

The production environment has the following Java Version.

Java Version  1.8.0_25

The Test and Training environment has the following Java Version.

Java Version  1.7.0_51 

Does anyone have any ideas?

Thanks,

Mike

[Carl Von Stetten]

I'd recommend having all of your environments on the same ColdFusion version and Java version.  This should allow you to reproduce production issues that are directly tied to ColdFusion functionality on your test environment.  In turn, this will help to isolate whether or not ColdFusion is the source of the problem.

[userCold9]

Hi,

The reason there is differenet level of Java is due to the ColdFusion builds.

This issue the users are encountering is affecting the some users because of the IE browser versions being used.

Per my research, making Test and Training environments the same a production takes time and is going to affect the on going development of enhancements.

Production code has not changed only the users browser versions of IE.

Thanks,

Mike

[Carl Von Stetten]

Again, most folks would recommend having all of your environments on the same version/update level of CF and Java.  Why? Because if you don't, eventually you will get a nasty surprise when some bit of functionality works perfectly on dev/test but fails on production because either a specific CF hotfix is missing, a newer hotfix introduces a regression, or the difference in JVM breaks some underlying dependency.  When (and it really is a matter of when, not if) this happens, trying to diagnose/debug will be a nightmare.

If all platforms are maintained on equal levels, those issues will be caught on dev/test and will never make it to production.

Then, when a new hotfix or version comes out, you apply it to dev first, thoroughly test your application, then apply it to test, thoroughly test again, and then you apply it to production.

Now, you said:

The reason there is differenet level of Java is due to the ColdFusion builds.

Now I'm confused - are all of your servers running the same version/hotfix level of ColdFusion or not (you're inital post seems to indicate they are all CF11 Update 3, but this statement seems to contradict that)?

Production code has not changed only the users browser versions of IE.

That may well be, but the underlying JavaScript libraries that power CFLayout/CFLayoutArea/CFAjaxImport may have been updated by a hotfix, and if all of your servers are on different hotfix levels, you might see different results on your client machines depending on which server they are accessing.