Unexpected sliding direction in a 2-image gallery
See original GitHub issueWhen the gallery only contains a total of 2 images, sliding direction is the opposite of what you would expect based on the order of the thumbnails. For example, when image #1
is active, and you click thumbnail #2
, you would expect that image #1
slides out to the left, and image #2
slides in from the right, however, it happens the other way around. Similarly, swiping left on image #1
results in a bounce and slide backwards, arriving on image #2
.
I haven’t had time to look into this in detail, but if nobody picks it up and you don’t have time either, @xiaolin, I might track this down sometime next week.
Issue Analytics
- State:
- Created 7 years ago
- Comments:10 (7 by maintainers)
Top Results From Across the Web
Image Gallery sliding in wrong direction on mobile - Jotform
You will see that when sliding from right to left the gallery images move to the right so that the pictures on the...
Read more >Content Jumping (and How To Avoid It) | CSS-Tricks
A web page isn't locked in stone just because it has rendered visually. Media assets, like images, can come in and cause the...
Read more >Prototype scrolling with overflow behavior - Figma Help Center
Scroll left-to-right to view different elements in a slider. Navigate between images, articles or posts in libraries and galleries. Pan or scroll around...
Read more >Optimize Cumulative Layout Shift - web.dev
In this guide, we'll cover optimizing common causes of layout shifts. The most common causes of a poor CLS are: Images without dimensions....
Read more >Unexpected behaviour order of images in slideshow
inc page. The problem i am having is that i am able to see the slide container 'rectangle box' but cant see the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I don’t have much time this week, but maybe next week if its not already fixed, I can take a look at it.
@gaborluk @texate this issue is now fixed in v0.6.6 🎉