Accessibility: Specify position of invisible/custom cursor - #197
Merged
Conversation
ulyssa
approved these changes
Jul 26, 2026
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
2 participants
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.
Not reporting an accurate terminal cursor can break accessibility tools like screen reader or braille displays. Windows like lists that implement a custom highlighting without updating the term cursor can now correctly position the cursor without changing the graphical output.
This is a breaking change but adding a default implementation for
hide_term_cursorthat just returnsfalseproved to be annoying when adaptingiambto this change. Because a lot of window types will use some sort of forwarding of all calls to inner types, all involved types need an explicit implementation of this function.addresses ulyssa/iamb#612