Skip to main content
Question

Routing Form Dropdown Display Bug on Mobile

  • October 28, 2025
  • 3 replies
  • 30 views

Hi everyone, I created my first routing form recently and noticed that on mobile views—and only on mobile!—the menu that displays your dropdown choices appears at the bottom of the view when the user clicks or taps the field.

 

This is an extremely non-standard behavior for a very well-defined and established UI paradigm of dropdown buttons where clicking a dropdown field will either expand from the field where the user clicked or in a worst case scenario, pop some kind of modal dialog. Calendly does neither here and confusingly shows the button at the bottom of the page. This should be reconsidered because it’s confusing to users and does not provide any kind of meaningful improvement to the experience.

 

You can see in my screenshot here that he desktop and tablet-width views both operate in a standard way when clicking the first dropdown menu at the top of the form, so the mobile behavior working like this is also an inconsistency that’s been introduced for no discernible reason. Please fix!

Desktop

 

Tablet
 



Mobile

 

3 replies

David
Community Manager
  • Community Manager
  • October 29, 2025

Hi ​@birdbambeth - Really appreciate the feedback here!

I’ve got this sent off to our product team to review! As it is right now, this is expected behavior within the Mobile UI, as drop-downs with multiple options can act a bit funky when using a touch screen.

Either way, I can see where you’re coming from here, hopefully we’ll see some changes here in the future!


  • New Community Member
  • November 24, 2025

Having the same problem - looked like page was stuck and disabled after clicking on a dropdown. After refreshing a few times I realized I could scroll further down to see the options.


  • New Community Member
  • December 11, 2025

this is super unintuitive and wrong from any UX standpoint. It is absolutely not possible to “know” that you must scroll down to the bottom. Is there any workaround or fix?  I just registered for this “feature” or intended behaviour like you put it….