You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, thank you for this wonderful component! Secondly, I've noticed an issue with Safari (Version 14.0 (16610.1.21.1.2)) and Chrome (Version 84.0.4147.135 (Official Build) (64-bit)) using 2.3.0.
I have two separate sections that contain a TextLoop each. One has a delay and the other doesn't. Their transition at first, works fine. However, when one switches to another tab, waits a dozen seconds or so and navigates back, their transitions end up synchronising and happen concurrently.
Steps to reproduce:
Add two TextLoop components to a page.
Set a delay on one of them to offset their transitions to be separated from each other.
Navigate to another tab.
Wait for a dozen seconds or so.
Navigate back
Expected results:
I'm not sure if the intended behaviour is already that the timers should pause when one navigates away from the tab, but perhaps that would be a good solution?
Again, thank you for your work on this component; it's an absolute joy to use.
The text was updated successfully, but these errors were encountered:
First of all, thank you for this wonderful component! Secondly, I've noticed an issue with Safari (Version 14.0 (16610.1.21.1.2)) and Chrome (Version 84.0.4147.135 (Official Build) (64-bit)) using
2.3.0
.I have two separate
section
s that contain aTextLoop
each. One has a delay and the other doesn't. Their transition at first, works fine. However, when one switches to another tab, waits a dozen seconds or so and navigates back, their transitions end up synchronising and happen concurrently.Steps to reproduce:
TextLoop
components to a page.delay
on one of them to offset their transitions to be separated from each other.Expected results:
I'm not sure if the intended behaviour is already that the timers should pause when one navigates away from the tab, but perhaps that would be a good solution?
Again, thank you for your work on this component; it's an absolute joy to use.
The text was updated successfully, but these errors were encountered: