Repository navigation
About: no on-screen keyboard over the system details - #76
Merged
Merged
Conversation
System > About opens fastfetch in a terminal. The tap on the menu entry counted for the terminal's text input coming on a moment later, so the on-screen keyboard came up and covered the details. About now tells the keyboard policy first (omarchy-keyboard quiet) that the window it opens is for reading: that tap no longer counts, and a tap in the terminal still brings the keyboard up.
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.
omarchy-keyboard quietclears the policy's touch windows, so About's terminal doesn't pop the keyboard. Rebased onto #74; keyboard policy tests pass, including the About test.Simulator-verified by Henrik.
Assisted-by: LLM