IE Compat Bridge

Legacy browser decision guide

IE mode or a Chrome compatibility bridge?

For legacy business apps, the safest answer is not always the same. Some pages need a real IE-compatible environment. Others only need a scoped JavaScript and DOM compatibility layer in Chrome or another Chromium browser.

Choose IE mode when the app needs IE itself

  • ActiveX controls, COM objects, Browser Helper Objects, or Windows-only browser plug-ins.
  • VBScript, Trident/MSHTML rendering, or strict IE document modes.
  • Enterprise Mode site-list governance, centralized browser policy, or a compliance requirement.
  • Pages that block non-IE engines before serving normal HTML.

Try a bridge when the page mostly works in Chromium

  • Framesets, loading redirects, old iframe access, or WebForms controls are the visible issue.
  • Errors point to attachEvent, window.event, event.srcElement, or document.frames.
  • Picker flows depend on showModalDialog but do not require native IE controls.
  • You can test one authorized hostname without broad website permissions.

A low-risk evaluation sequence

  1. List the failing workflow and the exact browser behavior that breaks.
  2. Identify whether the dependency is native IE technology or old JavaScript/DOM behavior.
  3. If native IE technology is required, use Edge IE mode, a Windows VM, remote desktop, or a managed legacy-browser service.
  4. If the page mostly works in Chromium, test IE Compat Bridge on one approved hostname first.
  5. Expand only after the workflow succeeds and the product boundary is clear to the site owner.
Install from Chrome Web Store Read the JavaScript guide

What this means for IT teams

IE mode remains the right operational tool when a system needs real IE capabilities. A compatibility bridge is a narrower test for pages that already run mostly in Chromium and only need selected browser-surface shims.

What this means for migration projects

A bridge can reduce pressure during migration, but it should not hide the inventory. Track each tested hostname, the broken workflow, the compatibility category, and whether full IE mode is still required.

IE Compat Bridge boundary

IE Compat Bridge applies JavaScript and DOM compatibility fixes only on configured and authorized domains. It is not an Internet Explorer engine and does not run ActiveX, COM, VBScript, Trident, Java applets, Browser Helper Objects, or true IE document modes.