Skip to main content
Question

Confirmation page bug for mobiles

  • March 11, 2026
  • 1 reply
  • 40 views
C

This is loaded from their official script: https://assets.calendly.com/assets/external/widget.js

Whats already set:

  • Container min-height: 700px (exactly what they suggest)
  • Container min-width: well above 320px (it's full mobile width, ~375px+)
  • We use overflow: hidden, clip-path: inset(0), contain: content on the .calendly-inline-widget class
  • We've added max-width: 100vw on the widget and its iframe via CSS

The actual problem:
The Calendly widget works fine on mobile until the user completes a booking. At that point, Calendly navigates its iframe to a "You are scheduled" confirmation page. That confirmation page's content is wider than the mobile viewport. Because it's a cross-origin iframe, mobile Safari ignores all CSS containment (overflow: hidden, clip-path, contain) on the parent and expands the entire page layout to fit the iframe content. This breaks the viewport for the current screen and all subsequent screens.

Key point : This is not an iframe sizing issue, it's specifically Calendly's confirmation page content inside the iframe being too wide for mobile viewports. The scheduling/calendar picker pages render fine. Only the post-booking confirmation page breaks things.

This is a bug in the confirmation page's responsive CSS, not in how we embed it. Can this be looked into?

1 reply

T
Employee

Hey there!

 

Thanks for taking the time to share such a detailed breakdown here.

 

Based on what you described, this does appear to be specific to the confirmation page shown after booking, rather than the initial embed setup on your site. Since the scheduling flow renders as expected on mobile and the layout only breaks once the iframe reaches the "You are scheduled" page, that points more to the responsive behavior of that confirmation state than to the container sizing or CSS applied outside the iframe.

 

I reviewed our official embed script and related internal tracking, and I’ve gone ahead and created a ticket for our Engineering team to investigate further.

 

To help us gather any additional details that may be needed for the investigation, please create a support ticket by emailing support@calendly.com and include both the title of this community thread and the web URL to it. That information will be best housed in our support channel, where our team can follow up directly for any additional examples or troubleshooting details and link your case to the ongoing investigation.

 

We really appreciate you calling this out and documenting the behavior so thoroughly.

Enroll in Calendly’s Research Community” style= Need Help? Visit 'Get Help. Give Help.'
Terms & ConditionsAccessibility statement