2892 views

Internet Explorer 11 - Not Recommended Browser


Recommend Migrating to Modern Browser

ServiceNow recommends that customers utilize a modern browser for it's products and migrate away from Internet Explorer 11 due to significant performance issues. 

 

Significant Performance Issues Compared to Modern Browsers

Internet Explorer 11 can be considerably slower, sometimes up to 2 times slower, when compared to other modern browsers on the ServiceNow platform.  Internet Explorer 11 is considered a legacy browser and is not recommended from a perspective of performance.

Reasons for sub-optimal performance in Internet Explorer 11

  • AngularJS (modern web development framework)
    • Starting in Fuji, ServiceNow began to use Angular JS which creates some additional overhead for browsers
  • Utilization of modern web and development standards
    • For example, ServiceNow uses inline scripting throughout the platform. Internet Explorer 11 has sub-optimal performance while parsing and executing inline JavaScript code.
  • Migration of UI15 to UI16
    • In Geneva+ ServiceNow migrated from UI15 to UI16 utilizing a lot more client-side functionality.  This exacerbates Internet Explorer 11 performance issues.
  • Browser memory leaks

 

Microsoft Statement on IE11 issues

Two critical aspects of browser performance are (1) javascript parsing and execution and (2) memory usage on the client.  Below is information regarding the performance of these areas as they relate to ServiceNow instances and information from Microsoft related to the sub-optimal performance of IE11:
 
Microsoft has confirmed with ServiceNow Development that they recognize IE11 processes are leaking memory under certain circumstances and confirmed this is a known issue. They have also clarified that IE11 has been a deprecated browser since January 2016. This issue actually affects not only ServiceNow but all websites using iFrames. We have seen an increase in reports of IE11 having performance issues since the release of Geneva due to the higher use of memory on the client.
 

Lastly, Microsoft is no longer fixing feature bugs (including this issue) and will be providing only security-related fixes for IE11.

https://developer.microsoft.com/en-us/microsoft-edge/platform/faq/will-internet-explorer-11-continue-to-re/

Microsoft bug reports

Microsoft reported the issue for their browser in the following reports:
https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/6768642/
https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/892089/
https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/7409348/

 

ServiceNow Workarounds (If Unable to Migrate)

Some recommendations to help alleviate IE11 memory leak issues are:
  • Reduce number of records in lists to 20
  • Reduce memory footprint of client-side code (custom UI scripts, client scripts, UI policies, revert to UI15, etc.)
  • Request end users to completely close and reopen their browsers after they have been in use for extended periods of time
  • Open all forms and lists outside of an iFrame on a separate tab
  • Disable automatic spell checking in IE11

Additionally, refer to the following Community post on Internet Explorer 11 process leaks memory in Windows 7

 

Additional Resources

ServiceNow Product Documentation | Browser Support

Gartner Report | Applying Bimodal to Browser Strategies: Legacy and Modern

Article Information

Last Updated:2018-04-27 08:40:06
Published:2018-04-27