Internet Explorer 11 is no longer officially supported by Webflow, which can lead to display issues across multiple Webflow websites viewed in that browser.
Use Progressive Enhancement:
Design your site to deliver a functional experience in IE11, but enhance the experience in modern browsers.
Avoid relying entirely on Flexbox or Grid for your layout if IE support is critical.
Add Fallback CSS:
Use older layout methods like floats or inline-block as a fallback.
You can add conditional class names with custom CSS targeting IE11 specifically using selectors like @media all and (-ms-high-contrast: none), (-ms-high-contrast: active)
.
Test Sites with Emulation Tools:
Use the IE11 emulator in Microsoft Edge or BrowserStack to catch rendering issues without needing an original IE11 install.
Disable or Simplify Interactions:
If animations cause breakage, remove or simplify them to degrade gracefully.
Use Custom Code to Detect and Warn Users:
Insert a simple JavaScript snippet to detect IE11 and display a warning banner suggesting browser upgrade.
Centralize and Reuse IE Fixes:
If managing multiple Webflow sites, create a shared list of common CSS patches for IE11 and apply them via Webflow’s custom code in the <head>
or <body>
sections.
Consider converting your fix list into small utility classes you can apply across projects.
Consider Redirecting IE11 Users:
Use JavaScript to detect IE (checking for document.documentMode
) and redirect them to an alternative page or show an unsupported browser message.
Webflow no longer supports Internet Explorer 11, so layout and interaction problems are likely across multiple sites. To mitigate them, you can use fallback CSS, disable complex interactions, and show warnings for users. If IE11 support is essential, use emulation tools and custom code workarounds—but consider encouraging users to upgrade to modern browsers.