Change Details

When the player is reparented we get a DOM removal event which prompts us to forget the player and transfer controls to another player. However, the player might just be reparented elsewhere. There's a race between we transfer controls to previous player on a different tab and us activating the player again when it reappeared.

We listen for the player being removed from the DOM so we can detect when a player was removed dynamically when e.g. an overlay div closes. However, when the player is just reparented elsewhere, we get a DOM add and remove dance, and then it becomes racy who will be given controls: previous player on another tab or the same player again when it becomes known again. To avoid this just ignore player removal when it remains part of the visible page DOM.

When the player is reparented we get a DOM removal event which prompts us to forget the player and transfer controls to another playere listen for the player being removed from the DOM so we can detect when a player was removed dynamically when e.g. an overlay div closes. However, when the player is just reparented elsewhere, the player might just be reparented elsewhere.we get a DOM add and remove dance, There's a race between we transfer controls to previous player on a different tab and us activating the player again when it reappearedand then it becomes racy who will be given controls: previous player on another tab or the same player again when it becomes known again. To avoid this just ignore player removal when it remains part of the visible page DOM.