Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(FEC-11156): cast button appears for one player only when multiple players configured on the page and casting failed #70

Merged
merged 5 commits into from
Nov 18, 2021

Conversation

SivanA-Kaltura
Copy link
Contributor

@SivanA-Kaltura SivanA-Kaltura commented Sep 20, 2021

Description of the Changes

Prevent calling CastLoader.load when multiple players are loaded one after the other
Distinguish between a casting and a non-casting player
Fixes FEC-11156

Related PRs:
kaltura/kaltura-player-js#495
kaltura/playkit-js-ui#640

CheckLists

  • changes have been done against master branch, and PR does not conflict
  • new unit / functional tests have been added (whenever applicable)
  • test are passing in local environment
  • Travis tests are passing (or test results are not worse than on master branch :))
  • Docs have been updated

@@ -60,6 +60,7 @@ class CastPlayer extends BaseRemotePlayer {
};

static _isAvailable: boolean = false;
static _loadPromise: any = null;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
static _loadPromise: any = null;
static _loadPromise: ?Promise<void> = null;

src/cast-player.js Outdated Show resolved Hide resolved
yairans
yairans previously approved these changes Nov 16, 2021
@SivanA-Kaltura SivanA-Kaltura merged commit 30595d8 into master Nov 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants