瀏覽代碼

fix(large-video): attempt to update large video on all connection updates

It is possible for a connection update to come during a large video update,
between its promises, which would result in the update NOT triggering another
large video update because an update is in progress. This can cause a state
where a connection status overlay is displayed over a video in a state that
does not match the actual video state, like the restoring overlay displaying
on active video.
j8
Leonard Kim 8 年之前
父節點
當前提交
538da92eae
共有 1 個文件被更改,包括 1 次插入7 次删除
  1. 1
    7
      modules/UI/videolayout/VideoLayout.js

+ 1
- 7
modules/UI/videolayout/VideoLayout.js 查看文件

@@ -702,13 +702,7 @@ var VideoLayout = {
702 702
     onParticipantConnectionStatusChanged (id) {
703 703
         // Show/hide warning on the large video
704 704
         if (this.isCurrentlyOnLarge(id)) {
705
-            // when pinning and we have lastN enabled, we have rapid connection
706
-            // status changed between inactive, restoring and active and
707
-            // if there was a large video update scheduled already it will
708
-            // reflect the current status and no need to schedule new one
709
-            // otherwise we end up scheduling updates for endpoints which are
710
-            // were on large while checking, but a change was already scheduled
711
-            if (largeVideo && !largeVideo.updateInProcess) {
705
+            if (largeVideo) {
712 706
                 // We have to trigger full large video update to transition from
713 707
                 // avatar to video on connectivity restored.
714 708
                 this.updateLargeVideo(id, true /* force update */);

Loading…
取消
儲存