Repository navigation
fix(zellij): keep tab swap checks on the captured plugin - #201
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Keep
Ctrl-f Wchecks tied to the status-plugin instance captured when the picker opens. Repeated discovery could elect another bar and report a false attachment change, leaving even current-tab selection open without reordering. The postmerge Linux failure showed the same client switching from plugin 7 to 6.Subsequent read-only queries validate the original client/plugin/server/nonce token and its picker focus. A missing, reloaded, detached, or refocused receiver still stops the swap. These checks validate the captured requester rather than requiring a complete all-client snapshot; stable tab IDs and full order checks remain in place. No new plugin permission or runtime patch is needed.
Follow-up to #199.