Hi @athena1979 ,
Thank you for reaching out, and I’m sorry for the trouble!
A large right-side margin appearing only on the mobile view is usually caused by either a margin or padding value applied somewhere in the menu (or its parent section/container) settings, or by a value being inherited from another element on the page that’s pushing the layout wider than the mobile viewport.
To help us pinpoint the exact cause and provide an accurate fix, could you please share the following?
- The URL of the page where the issue is occurring
- A screenshot showing the extra margin/scroll on mobile
- If possible, a short screencast (e.g., via Loom or a similar tool) demonstrating the behavior
With these details on hand, we’ll be able to inspect the layout closely and recommend the most accurate solution for you.
Looking forward to your response!
Best Regards,
I actually think it is the dropdowns in the menu that are causing the issue (it’s happened on multiple sites, so it is not a value I am adding in myself). I have solved the problem by switching to the flyout menu when the site is viewed on tablet or mobile (not ideal, but it works for now).
Hi @athena1979 ,
Thanks for your response.
While we haven’t been able to replicate this behavior in our test environment yet, I can see it’s still causing trouble on your end.
Could you please share a direct link to a page where this is happening? Having the live URL will allow me to inspect the page code directly and pinpoint exactly what’s triggering that unwanted spacing. Once I can see it in action, I’ll be able to provide a definitive fix!
Looking forward to your response,
Regards,
Plugin Support
Dhruv
(@dpandya)
Hi @athena1979,
Just checking in on this thread since we haven’t heard back. It sounds like the flyout menu workaround is keeping things stable on tablet and mobile for now, which is good to hear.
We’d still be interested in taking a closer look at the dropdown-related spacing issue if you’re able to share more details such as screenshot of the configuration and the issue along with the URL where we can inspect it directly, that would help us replicate the behaviour and confirm whether it’s something to address in the widget itself.
For now, we’ll mark this thread as resolved given the workaround is in place. If you have a chance to share that URL later, or if the issue resurfaces in a different way, please feel free to reply here or open a new thread and we’ll pick it back up.
Best regards,
Dhruv – BSF Support Team
