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
Not sure if this is an issue with this component or the youtube player itself, but reporting here nonetheless.
Current Behavior
I have a youtube video to be configured to start at a certain time. At the start there are times where the value is still not the newest, but is updated a milliseconds after.
The problem is that if the player gets ready with the first value, then even if it's updated to the new value, it will still use the first value.
This is without even clicking the play button.
Hi @LoyalPotato , This issue is not related to the youtube player. It is related to how we configure our component to re-render.
In your code there is no way the Player Component knows that some configure option value changed as the configure option is an object and react checks the object reference which won't trigger a render of the component even though one its props changes. We need to trigger a render for the player component and we could use key property to make this happen.
I have updated your code here to work properly for your scenario, Please check!
Not sure if this is an issue with this component or the youtube player itself, but reporting here nonetheless.
Current Behavior
I have a youtube video to be configured to start at a certain time. At the start there are times where the value is still not the newest, but is updated a milliseconds after.
The problem is that if the player gets ready with the first value, then even if it's updated to the new value, it will still use the first value.
This is without even clicking the play button.
Expected Behavior
Expected it to use the most recent value.
Steps to Reproduce
You can see it here:
https://codesandbox.io/s/crazy-babbage-g9owgs?file=/src/App.js
Environment
https://www.youtube.com/watch?v=KRIBVykhpC4
Brave (Chromium)
MacOS 13.2.1 (22D68)
The text was updated successfully, but these errors were encountered: