-
Notifications
You must be signed in to change notification settings - Fork 38
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
Clicking zoom buttons interrupts slideshow playback #331
Comments
Please translate to English. |
When I open the photo preview, I click the wheel map button to start the wheel, when I reach a certain image, I click the enlarge button, I can normal wheel blog, Then, when the wheel bo goes to the next one, continue to click the enlarge button, and the wheel Bo map will be stuck, and the status of the button is not updated in time. In the case of mobile terminal, h5, click the button to start the wheel Bo, and after the wheel Bo starts, click the button to enlarge the picture, and the wheel Bo effect will be stuck directly In summary, after the wheel starts, clicking the zoom button will terminate the wheel, and the status of the corresponding wheel button is not updated in time Expected behavior Two ways
2, after the start of the wheel, click the zoom and zoom button, will not interrupt the playback of the wheel
|
Thank you. I was able to obtain the following translation with Google Translate.
I'll publish a fix implementing approach #2 - clicking zoom in / zoom out buttons should not interrupt slideshow playback. |
🎉 This issue has been resolved in version 3.21.8 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Describe the bug
当我打开照片预览时,我点击轮博图按钮,开始轮博,到某一张图时,我点击放大按钮,可以正常轮博,
然后等轮博到下一张时,继续点击放大按钮,轮博图就卡住了,并且按钮状态没有及时更新,在移动端,h5情况下,点击开始轮博的按钮,开始轮博后,点击放大图片按钮,轮博效果就直接卡住了
总结,轮博开始后,点击点击放大按钮会终止轮博,并且对应轮博按钮的状态没有及时更新
Expected behavior
两种办法
1、轮博图开始时,可以禁用放大和缩小按钮
2、轮博开始后,点击放大和缩小按钮,不会中断轮博图的播放
3、轮博开始后,可以点击放大和缩小按钮,点击之后,轮博正常终止,轮博图按钮的状态正常更新即可
How to reproduce
https://react-photo-album.com/examples/lightbox
在移动端的情况下使用
Screenshots / Logs
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: