Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IgxCarousel - Slides do not transition properly by pan gesture. #12208

Closed
mkamiishi opened this issue Oct 20, 2022 · 8 comments
Closed

IgxCarousel - Slides do not transition properly by pan gesture. #12208

mkamiishi opened this issue Oct 20, 2022 · 8 comments

Comments

@mkamiishi
Copy link

Description

Slides do not transition properly by pan gesture.

  • igniteui-angular version: 14.2.2
  • browser: Safari, iOS 15.7

Steps to reproduce

  1. Run the attached sample on iPhone.
  2. Scroll the slides left and right continuously by pan gesture.

Result

Scrolling sometime stops in the middle of the slides transition.

Expected result

Scrolling do not stop in the middle of the slides transition.

Attachments

carousel.zip

@mkamiishi mkamiishi added the 🐛 bug Any issue that describes a bug label Oct 20, 2022
@simeonoff simeonoff self-assigned this Oct 24, 2022
@simeonoff simeonoff added 🛠️ status: in-development Issues and PRs with active development on them and removed 🆕 status: new labels Nov 6, 2022
@mkamiishi
Copy link
Author

Hi,
Customer asks when this issue will be fixed.

@simeonoff
Copy link
Collaborator

Hi @mkamiishi , I spent the better half of the afternoon trying to figure this out. It seems there's an ongoing issue with the touch gestures library we use. Since we allow users to scroll while also panning, the panend event never gets fired (third-party issue), hence why the slide appears to freeze in the middle of the transition. I will communicate with other colleagues in the company to see if we can come up with a solution, as it doesn't seem likely that it will be fixed by the Hammer.js team.

@mkamiishi
Copy link
Author

Any updates on this?

1 similar comment
@mkamiishi
Copy link
Author

Any updates on this?

@simeonoff
Copy link
Collaborator

@hanastasov Can you guys check if there's any way to improve the gestures UX in iOS 13+ given the limitations of hammerjs?

@hanastasov
Copy link
Contributor

@hanastasov Can you guys check if there's any way to improve the gestures UX in iOS 13+ given the limitations of hammerjs?

Yes, sure. @dobromirts will have a look at that. Thanks for the information you provided based on your testing!

@hanastasov
Copy link
Contributor

as @dobromirts pointed out to me, hammerjs seems unsupported for quite a long time now, we dont expect this to be resolved by them. we wiil try one of the suggested work arounds in a topic linked by Simeon, but only implement it if everything goes smooth and without blockers.

Otherwise I dont think the effort is worth it to fix a platform specific bug that does not block a user from using the component

@mkamiishi
Copy link
Author

I'm closing this ticket as a third-party issue.
Thank you again for investigating this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants