Safari bug: oversized Google Meet / Zoom / Teams icons block the booking form (inline embeds and booking pages)
Hello everyone,
For several days, the booking form is broken on Safari when an event offers Google Meet, Zoom or Microsoft Teams as a location option. I first noticed it on my own inline embed, then tested several other websites using Calendly: the problem is everywhere.
What happens
At the "Enter details" step, the location icon (Google Meet, Zoom or Teams) is rendered at a huge size and overlaps the fields below it (the phone number field in my case). Clients can't properly select a meeting type, and in practice many of them simply can't book.
Environment
- Affected: Safari on macOS and Safari on iOS/iPadOS (same WebKit engine)
- Not affected: Chrome and Firefox, desktop and mobile
- Safari version tested: 27.0 (22625.1.29.11.27)
Steps to reproduce
- Open any Calendly booking page or inline embed whose event offers Google Meet, Zoom or Teams as a location
- Pick a date and a time
- On the "Enter details" step, look at the location choices
Measurements (Safari accessibility tree)
- "Google Meet" radio button: 164 × 141 px
- "Phone call": 167 × 23 px
- "FaceTime" (custom location, no brand icon): 82 × 20 px
The icon really is rendered at this size in the layout. It's not a visual glitch. Custom locations without a brand icon display correctly.
Likely cause
This looks like a known WebKit behavior with SVG icons: when the referenced symbol has no explicit width/height, Safari can fall back to the intrinsic size and ignore the CSS constraint, while Chromium and Gecko apply it correctly.
Impact
Safari is a very large share of traffic, especially on mobile. For solo professionals and small businesses, a blocked booking form means lost appointments and lost revenue, and most account owners probably don't know it's happening because they test in Chrome.
I contacted support several days ago and haven't received an answer yet. Could someone from the Calendly team confirm the issue and share an estimated fix date?
If you're affected too, please reply with your browser and OS version so this gets the visibility it needs.
Thanks,
David