Member Junction
    Preparing search index...

    Which channel surfaces the call overlay's stage (mj-media-stage) holds, and where each one shows.

    Placement. Every surface starts where its channel's registry row places it (SurfacePlacement: its tab, unless the row says otherwise). The user moves it to the stage (it fills the call), into a picture-in-picture box, to its tab, or out of sight, within the placements the row allows; the moves are kept in order, one per surface, and resolved by ResolveSurfacePlacements, so the most recent move to the stage wins it, the surface it displaces returns to where its channel places it, and picture-in-picture boxes stack newest first. The host saves Moves and loads them back (LoadMoves), so a layout carries over to later sessions.

    Creation. A channel's surface is created the first time it is seen (its tab shows it, or it is on the stage or in a picture-in-picture box) and kept until the channel leaves the session. Moving it, hiding the panel or switching tabs only changes where it shows, so a whiteboard keeps its view and a stream keeps playing.

    Pure state with no Angular: the overlay reports the session's channels, the channel tab the panel is showing and the user's moves, and binds Surfaces to the stage.

    Index

    Constructors

    Accessors

    Methods