fix(vidstack): provider load connect race#1840
Merged
Merged
Conversation
mihar-22
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixes #1836 by preventing the provider loader from running before the
MediaProvidercomponent has connected and installed its source-selection setup effects.The provider now records the media target passed by early refs, defers loader execution until
onConnect, and replays the stored target afterSourceSelection.connect()is active. This addresses the production/IIFE timing case where an inlined lazy provider import can resolve immediately and fireprovider-changebeforemedia-player-connect, leavingprovider-setuppermanently missed.