Internet Explorer (IE) compatibility issues can occur because Webflow-generated sites use modern HTML, CSS, and JavaScript features not supported by IE. Here’s how you can address or work around those issues.
1. Understand IE’s Limitations
- IE11 is the last supported version, and even that lacks full support for CSS Flexbox, Grid, CSS variables, and modern JavaScript (ES6+).
- Microsoft recommends using Edge; IE is considered deprecated as of June 15, 2022.
2. Identify What’s Broken in IE
- Use BrowserStack or similar tools to preview your Webflow site in IE.
- Manually test on an IE11 installation (if available).
- Make a list of broken layouts or non-functional scripts.
3. Adjust CSS Features in Webflow Designer
- Avoid CSS Grid—IE doesn’t fully support modern Grid. Use Flexbox with caution (ensure no auto margins or wrapping tricks).
- Avoid custom properties (CSS variables)—Webflow may inject them in custom code or embed code.
- Use fallback properties for any CSS that may not be recognized.
- Stick to widely supported CSS units and properties (avoid
clamp()
, min()
, max()
).
4. Use Feature Detection or Fallbacks in Custom Code
- If you’re using custom JavaScript, use feature detection (e.g.,
typeof Promise !== 'undefined'
) to check if IE supports it. - Avoid ES6 syntax (like arrow functions or
let/const
) unless transpiled.
5. Add a Browser Upgrade Notice
- Consider adding a banner or modal popup using Webflow interactions or custom JavaScript to inform users they’re using an outdated browser.
- Example content: “This site uses modern web technologies. Please upgrade your browser for the best experience.”
6. Use Polyfills (Optional but Limited)
You can include polyfills (from services like Polyfill.io) to patch certain missing JavaScript features.
Include a script tag in Project Settings > Custom Code > Head Code:
Example (inline use only):
https://polyfill.io/v3/polyfill.min.js?features=default
Note: Polyfills have limited impact on CSS compatibility.
7. Avoid Webflow Features That Rely on Modern APIs
- Animations built with Interactions 2.0 may not run reliably.
- Lottie animations may not work in IE or render incorrectly.
- Sliders, tabs, and dropdowns are generally safe, but test them.
8. Consider Dropping IE Support
- Usage of IE globally is below 1%. If your audience doesn't rely on it, you may choose to:
- Include messaging rejecting support for IE, or
- Redirect IE users to a static fallback or message page using custom code.
Summary
To resolve IE compatibility issues in Webflow, stick to basic layout structures, avoid modern CSS/JS features, test thoroughly, and optionally inform users to upgrade. Full compatibility isn't guaranteed due to IE's legacy nature, and long-term support is not advisable.