[Mobile] Scrolling on page instead of sliding

[Lansenou]

Describe the bug
When I'm using the Slider and I happen to slide the tiniest bit up/down instead of sideways, the slide action is released and instead I'm scrolling on the page. The Slider is now stuck at the last value. It doesn't always occur, but most of the time it does.

To Reproduce

1. Have a page with enough content to slide vertically on it when using a phone/tablet.
2. Start a slide action and slide a bit vertically.
3. Notice how the slider has stopped and instead you're scrolling on the page.

Expected behavior
I'd expect the slider to consume all inputs, to block all vertical movement, and thus block scrolling on the page.

Screenshots
https://github.com/user-attachments/assets/8d0ab92e-54a8-427c-9e85-6b304a6f856d

Informations (please complete the following information):

• OS: iOS
• Browser/App: App
• Bubble Card version: 3.0.0-beta.7 (been happening since the start of 3.0.0)
• Home Assistant version: 2025.5.1 (also with 2025.4)

[Clooos]

Hi! I just tried on iOS and I don't have this issue on my side. Can you check in the editor of any Bubble Card, at the bottom you can see the version, there is currently an issue with HACS and some updates are not correctly updated.

Or I might have fixed that by fixing some other issues, if you really are in v3.0.0-beta.7, just wait for the next release 🙂

[Lansenou]

It's fixed in v3.0.0-beta.8! Thank you 🥳 !

[Lansenou]

Beta v3.0.0-beta.9 seems to have reintroduced this issue for me.

[Clooos]

Again, just to be sure, have you checked the version in the editor? (I really can't wait for the HACS issue to be fixed 😅)

Edit: And indeed it was fixed in v3.0.0-beta.8, because scrolling on the page was fully deactivated, and this was fixed in beta.9 😅 But there is probably something I can do about that.

[Lansenou]

Again, just to be sure, have you checked the version in the editor? (I really can't wait for the HACS issue to be fixed 😅)

Yes, I checked the version in the editor.

[Clooos]

Ok, good to know! I will check that then! This issue is the only one remaining in my list (at least for now 🤞), so after fixing this, I should finally have a good candidate for the final v3.0.0 beta! 🎉