Getting warning 'video is being deferred until the player has loaded'
See original GitHub issueI’m getting this warning every time player is trying to load my video. It works fine when it loads the video for the first time, but after that for all other videos it shows a glimpse of previous video and then loads the actual one.
How can I wait for the player to fully load before sending in the url?
This is my what my code looks like:
<ReactPlayer
playing={false}
controls={true}
url={this.props.movieVid}
/>
I’m probably doing something wrong here. It’d be great if you can help me out with this issue! p.s. thanks for your amazing work!
Issue Analytics
- State:
- Created 5 years ago
- Comments:14 (5 by maintainers)
Top Results From Across the Web
Getting warning 'video is being deferred until the player has ...
The solution is to not change the url prop too quickly. This happens when a player tries to load but url changes before...
Read more >FV Flowplayer Video Player – Extensió del WordPress | WordPress ...
FV Player is a free, easy-to-use, and complete solution for embedding FLV or MP4 videos into your posts or pages. With MP4 videos,...
Read more >Deferred Shading rendering path - Unity - Manual
This page details the Deferred Shading rendering pathThe technique that a render pipeline uses to render graphics. Choosing a different rendering path ...
Read more >reactjs - Black Video Screen when attempting to load a video ...
I am attempting to load a local video into react using react-player to play the video. I have the basic code setup but...
Read more >Safari Technology Preview Release Notes - Apple Developer
Changed to make sure nested worker gets controlled if matching a service worker ... computed from presentational hints before the video loads (255743@main) ......
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
Ah yeah, changing
url
rapidly (like in a test) is likely to trigger that warning. That’s annoying.I’m considering getting rid of that guard altogether, or at least a prop that avoids it. It seems to cause more problems than it solves.
Also having the same problem as @MitchelSt as well.