When interacting with the swipers left side, it works like expected. On the right side, it's likly, the touch event is propagated to kirby-page and captured as a swipe back gesture.
## Describe how to reproduce the bug
I have not been able to reproduce it in cookbook, but assume that it has something to do with the usage of kirby-page together with kirby-slider.
The bug appear when kirby is used in a webview. It happens on both Samsung Tab A and iPad, though less pronounced on latter.
Which Kirby version was used?
9.3.2
## What was the expected behavior?
To have the same behaviour for kirby-slides regardless of the touch event's position.
It looks like the bug is easier to reproduce in landscape than portrait.
When I attach a cable and use chrome://inspect the bug goes somewhat away and reappear the instant the cable is unplugged.
Checklist:
The following tasks should be carried out in sequence in order to follow the process of contributing correctly.
Verification
To make sure the bug is not intended behaviour; it should be verified by a member of team Kirby before moving on to implementation.
[ ] Make sure the NOT verified label has been removed by a member of team Kirby; do not proceed until this is done.
Implementation
The contributor who wants to implement this issue should:
Describe the bug
When interacting with the swipers left side, it works like expected. On the right side, it's likly, the touch event is propagated to kirby-page and captured as a swipe back gesture.
## Describe how to reproduce the bug I have not been able to reproduce it in cookbook, but assume that it has something to do with the usage of kirby-page together with kirby-slider. The bug appear when kirby is used in a webview. It happens on both Samsung Tab A and iPad, though less pronounced on latter.Which Kirby version was used?
9.3.2
## What was the expected behavior? To have the same behaviour for kirby-slides regardless of the touch event's position.Add any screenshots
https://streamable.com/90kxnp
Are there any additional context?
It looks like the bug is easier to reproduce in landscape than portrait. When I attach a cable and use chrome://inspect the bug goes somewhat away and reappear the instant the cable is unplugged.
Checklist:
The following tasks should be carried out in sequence in order to follow the process of contributing correctly.
Verification
To make sure the bug is not intended behaviour; it should be verified by a member of team Kirby before moving on to implementation.
NOT verifiedlabel has been removed by a member of team Kirby; do not proceed until this is done.Implementation
The contributor who wants to implement this issue should:
Review
Once the issue has been implemented and is ready for review: