Repository navigation
fix: keep composer mention menu with the caret - #1140
Merged
Merged
Conversation
Model: gpt-6
Model: gpt-6
Model: gpt-6
Model: gpt-6
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.
Related issue
None. This is an internal composer mention-placement regression.
Problem
Anchoring the main chat menu to the composer frame disconnected it from the caret. The floating positioner could then place a tall menu below the caret even when several rows fit above. Its inline viewport-sized max-width also overrode the input-width cap, stretching long command descriptions off the right edge.
Summary
Verification
Context handoff
Internal same-repository branch; external contribution handoff is not applicable.