Fix player refs not setting correctly. #868
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I described an issue I encountered here on the demo.
#867
I then experienced this same problem in my own code, where
seekTo
wasn't working correctly. It turns out that the issue was actually far more widespread, and the ref just wasn't being set at all.When I logged out the object in
ReactPlayer
that was calledrefs
, which was meant to hold two functions to set refs in child components, it was an empty object. This appears to be a reserved keyword that is presumably used by react, as it was being overridden with an empty object. Simply changing the property name fromrefs
tosetRef
resolved the issue, and seeking behavior (among other things) now work correctly.In order to test: follow the steps in the issue I linked above, and notice the broken behavior. Then test the same behavior in this branch, and note it functioning correctly.