"autoPlay is triggered more than once" since v0.22.0
See original GitHub issueSince 0.22.0
(and latest 0.23.1), I am now getting autoPlay is triggered more than once
repeatedly in the console. React 15.5.4
.
static defaultSliderProps = {
arrows: true,
autoplay: true,
autoplaySpeed: 4000,
dots: false,
draggable: false,
fade: true,
infinite: true,
lazyLoad: 'progressive',
slidesToShow: 1,
slidesToScroll: 1,
speed: 1000,
waitForAnimate: true,
};
Reverting to 0.21.0
doesn’t show this error.
Will try to replicate later on today in codesandbox.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:5
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Video auto play is not working in Safari and Chrome desktop ...
starts playing automatically once the page is loaded in FireFox but cannot do autoplay in Webkit based browsers. This only happened on some...
Read more >Autoplay guide for media and Web Audio APIs
Automatically starting the playback of audio (or videos with audio tracks) immediately upon page load can be an unwelcome surprise to users.
Read more >How to turn off autoplay videos on Facebook, Twitter, Firefox ...
Scroll down until you find “Media and Contacts,” then tap “Videos and Photos.” Finally, once you find “Autoplay,” you can turn off the...
Read more >Autoplay videos - YouTube Help - Google Support
The Autoplay feature on YouTube makes it easier to decide what to watch next. When Autoplay is on, another related video will automatically...
Read more >Autoplay policy in Chrome - Chrome Developers
# Media Engagement Index · Consumption of the media (audio/video) must be greater than seven seconds. · Audio must be present and unmuted....
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 Free
Top 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
I’ll surely take a look at this.
It’s been fixed and will be released with 0.23.0.