fix(connections): let Tab leave the AI rules text field via the key view loop (#1490)#1517
Merged
Conversation
Signed-off-by: Ngô Quốc Đạt <datlechin@gmail.com>
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
1 participant
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.
Part of #1490 (keyboard, focus, accessibility). Connection form.
The AI rules field is a plain (non-code)
NSTextView, but it trapped Tab as an inserted tab character, so keyboard users could not move past it. This addstextView(_:doCommandBy:)to the delegate to routeinsertTab:/insertBacktab:towindow.selectNextKeyView/selectPreviousKeyView, the standard AppKit mechanism for a text field that should participate in the key view loop.Native delegate hook, no subclass. Lint clean, style gate clean.