Starting in Looker 22.16, Internet Explorer 11 (IE11) is no longer supported for use with Looker. If you prefer or are required to use a Microsoft browser, for the best experience with Looker we suggest that you use Microsoft Edge, which is supported at Level 1.
If you are currently using IE11, we recommend you switch to Edge or another Level 1 supported browser.
Why is Looker changing this?
In 2015, Microsoft released the Edge browser as a replacement for IE. As Internet Explorer no longer receives major updates, it misses the latest security patches and new functionality for complex web apps like Looker.
Looker strives to deliver products that meet our customers' needs. The increasing gap between IE11 and all other browsers has caused a disproportionate amount of effort relative to the user base to avoid and fix defects specific to the browser. This limits our technology choices and dampens our ability to deliver the reliability and functionality our customers expect.
IE11 can be considerably slower, sometimes up to 10 times slower, when compared to other modern browsers on the Looker platform. IE11 is also susceptible to memory leaks which may impact performance, especially in Windows 7. IE11 is considered a legacy browser and is not recommended from the perspective of performance. For example, see the Internet Explorer 11 process leaks memory in Windows 7 (not the JS Heap) ServiceNow article about memory leaks with iframes.
What do I need to do?
We recommend that you update your systems to ensure that your users are on a Level 1 supported browser. See the Supported browsers documentation page for a list of Looker supported browsers.
Workarounds (if you are unable to migrate)
To help alleviate IE11 memory leak issues, request end users to completely close and reopen their browsers after they have been in use for extended periods of time.
In contexts where Looker content is embedded using iframes, we recommend that if you are supporting IE 11 use that you design your application to reduce the memory footprint of client-side code and iframe usage.