Touch support for carousel

Radzen.Blazor Components
1

Is there a official support for touch on the Carousel component?

Because currently you can swipe the carousel items, probably due to the css of the items, without the component taking notice. So you swipe to the nex item, the pager stays where it was and on auto rotate it will jump back to the "next" item without regards for what is displayed currently.
I'm just not sure, what is intended behaviour for the component.

2

We will do our best to fix this before the end of the week.

3

I am having a weird experience with the carousel. I have additional controls inside the carousel content. On desktop it works fine. On a mobile screen, the carousel does respond to touch but

  1. Scrolling left or right based upon touch is erratic. It jumps around and the pager doesn't adjust accordingly.
  2. There are no click events on the controls within the carousel content.
4

I think we can improve this in our next update on Monday.

Can you point us to some of our demos where I can reproduce the behavior?

5

Yes, on the examples go to the data-binding example and set Auto=false. Toggle your browser in developer tools to a phone size. Scroll a bit on the details section until you get a column filter button and try to click the column filter. Nothing happens. When I go to the separate demo of the column filter in phone size dimensions the filter does work. Once you switch to responsive it also works even when resizing it to the phone size dimensions. Also tested this on a real phone with the same result.

Have not been able to replicate the erratic scrolling on the desktop. But the left/right swipe isn't really available either like it is on a phone. I will dig further into that but it is very specific to swiping.

6

I was unable to replicate it too that’s why I asked for details. As I already noted we will fix the unable to touch issue in our update on Monday.

7

@enchev I was finally able to pinpoint the erratic scrolling issue, but was never capable of reproducing it in your demos. What was happening: browser-based css scrolling was conflicting with control based scrolling to a specific element. So if you gave the control a big enough swing, the browser based smooth scrolling was ongoing and somewhere during that Blazor would make the javascript call to scroll to a specific item. It became a race condition of sorts.