From a technical standpoint, the only real change is that our code moved from an NPAPI. But Chrome removed NPAPI support, so we were forced to implement a new solution, and that solution requires a separate helper executable. IE Tab used to use that functionality to access the Internet Explorer rendering engine. Chrome used to support a technology called NPAPI (the Netscape Plugin API) which allowed extensions to access local computer resources. Did IE Tab always require this extra program? This rendering engine can't be directly accessed from a Chrome extension, so we need a helper process to communicate between the Chrome extension and the rendering engine.Ģ. IE Tab uses the Internet Explorer rendering engine. Why do I have to install ietabhelper.exe? * Use Java, Silverlight, and ActiveX in Chrome seamlesslyġ. * Edit Sharepoint documents instead of opening read-only * Securely use the old IE rendering engine * Group Policy support for enterprise deployments * Create a list of URLs that will automatically open in IE Tab You can read more about that in the FAQ below.Ī license is required for non-personal use of all versions of IE Tab, and IE Tab Enterprise has more strict license enforcement. Please note that IE Tab for Windows does require the use of a separate executable, ietabhelper.exe. IE Tab exactly emulates Internet Explorer, and enables you to load your web pages with different versions of IE (IE7 - IE11)įULLY SUPPORTED IN WINDOWS 11 AND AFTER INTERNET EXPLORER IS REMOVED IN FEBRUARY 2023. Use Java, Silverlight, ActiveX, Sharepoint, and more.

Display web pages using IE within Chrome.

Silverlight on mac chrome