-
Notifications
You must be signed in to change notification settings - Fork 8.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[A11y] Treat last character as 'end of buffer' #10516
[A11y] Treat last character as 'end of buffer' #10516
Conversation
TODO
|
Most of the code that's submitted won't be touched, so a review would be much appreciated! |
Bug:
NVDA says, on each press of backspace: "h, h, s, s". NVDA should say (and said before this PR): "space, h, s, s". |
{ | ||
return bufferSize.EndExclusive(); | ||
} | ||
// if we're already on/past the last RegularChar, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not quite the last regular char. We need (user-entered) spaces, just not the extraneous thousands of newlines.
a99fa3c
to
84fdf5a
Compare
@carlos-zamora automerge broke this |
Urgh. I rebased it locally, but haven't pushed the changes yet. I'll fix this on Monday. Thanks. |
Summary of the Pull Request
Updates our
UiaTextRange
to treat the last legible character as the end of the buffer. Doing so significantly improves performance of word navigation because screen readers no longer have to take into account the whitespace following the end of the prompt.This also fixes #7960. This bug was caused by the
UiaTextRange
occasionally having its_blockRange
member set totrue
. As a result, the screen reader would read the block range of text from "start" to "end" as if it was a block selection created by Alt+Mouse.References
#7000 - Epic
Closes #6986
Closes #7960
Detailed Description of the Pull Request / Additional comments
Coming soon!
Validation Steps Performed