If your Webflow site displays layout issues in Safari on iPad or MacBook Air, it could be due to browser-specific rendering quirks or unsupported CSS features.
1. Check for Safari-Specific CSS Incompatibilities
- Safari on iOS and macOS may not fully support the latest CSS features used in Webflow.
- Look out for issues with flexbox, grid, vh/vw units, or backdrop-filter, which sometimes behave differently in Safari.
- Use Can I Use (caniuse.com) to verify compatibility of any advanced CSS you’re relying on.
- On a MacBook Air, open Safari and go to Develop > Show Web Inspector.
- Enable device simulation for iPad to spot layout issues.
- Look for any differences in computed styles, box dimensions, or JavaScript errors.
3. Test Layout Inside Webflow Designer
- In Webflow, use the tablet and mobile preview modes, especially the iPad landscape setting.
- However, keep in mind: Webflow Designer previews do not exactly replicate how Safari renders things on physical Apple devices.
4. Use Overflow or Fixed Position Responsibly
- Safari can have problems rendering elements with overflow:hidden, position:fixed, or 100vh units, especially within nested containers or modals.
- Consider using min-height: 100vh or custom JS to calculate height on load if needed.
5. Try Adding -webkit- CSS Prefixes (Via Custom Code)
- For some effects (e.g., custom scroll, filters), Safari may still require -webkit- prefixes.
- These can be added under Project Settings > Custom Code or Page Settings > Custom Code.
6. Verify Font Rendering and Line Height
- Safari may render fonts with slightly different line-height or letter-spacing.
- Avoid relying on exact pixel alignment between elements if you’re using custom fonts.
7. Clear Cache and Test on Actual Devices
- Confirm layout issues on real iPads or MacBooks, not just simulators.
- Clear Safari cache to ensure you’re not viewing an outdated version of your CSS or Webflow export.
Summary
Safari layout issues on iPad or MacBook Air usually stem from CSS compatibility differences, vh/vw sizing, or unsupported properties without -webkit- prefixes. Use Safari’s Web Inspector to pinpoint problems, and test on real devices to ensure consistent rendering.