the "last-n" notification is the source of truth for clients as to which streams they're receiving from the bridge. Therefore, it's best to rely on that as the trigger for local layout changes. If a client pins another client, it doesn't automatically get a new last-n notification which it would normally rely on to actually perform a switch. This change automatically sends an updated last-n notification when a pin/unpin occurs that changes the pinned list.
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: