Skip to content
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

Revert "Use UIA caret events in Windows Terminal (#16873)" #17048

Merged
merged 2 commits into from
Aug 27, 2024

Conversation

codeofdusk
Copy link
Contributor

@codeofdusk codeofdusk commented Aug 23, 2024

Link to issue number:

Reverts #16873.

Summary of the issue:

  • When backspacing beyond the leftmost character of a line in Windows Terminal, the last character of the prompt is erroneously read in some environments.
  • Some caret tracking issues (especially when connected to remote systems) are more apparent.

Description of how this pull request fixes the issue:

Revert the new behaviour until it can be fixed upstream or a workaround can be found.

Testing strategy:

Verified restoration of previous behaviour and that caret tracking works as before.

Known issues with pull request:

Please include in 2024.4.

Code Review Checklist:

  • Documentation:
    • Change log entry
    • User Documentation
    • Developer / Technical Documentation
    • Context sensitive help for GUI changes
  • Testing:
    • Unit tests
    • System (end to end) tests
    • Manual testing
  • UX of all users considered:
    • Speech
    • Braille
    • Low Vision
    • Different web browsers
    • Localization in other languages / culture than English
  • API is compatible with existing add-ons.
  • Security precautions taken.

Summary by CodeRabbit

  • New Features

    • Reinstated reliance on UIA events for caret movement in XAML and WPF text controls, improving caret tracking accuracy.
    • Updated Seika Notetaker driver for better braille input handling.
  • Bug Fixes

    • Adjusted on-demand speech mode to reduce interruptions during specific actions.
    • Fixed garbage character output in braille when accessing Microsoft Word without UI Automation.
    • Improved braille cursor routing for better navigation with Unicode characters.

@codeofdusk codeofdusk requested a review from a team as a code owner August 23, 2024 22:39
@codeofdusk codeofdusk requested a review from seanbudd August 23, 2024 22:39
Copy link
Contributor

coderabbitai bot commented Aug 23, 2024

Walkthrough

The recent updates to NVDA include bug fixes and enhancements focusing on caret movement detection, improved braille input functionality, and the suppression of unnecessary speech output in specific scenarios. These changes restore reliance on UIA events for caret tracking in XAML and WPF, adjust the Seika Notetaker driver for better braille input, and enhance the overall braille navigation experience.

Changes

Files Change Summary
source/NVDAObjects/UIA/winConsoleUIA.py Removed the _get_caretMovementDetectionUsesEvents method, affecting caret movement detection logic.
user_docs/en/changes.md Restored UIA event reliance for caret movement in XAML/WPF, updated Seika Notetaker driver, adjusted on-demand speech mode, fixed braille character output in Microsoft Word, and improved braille cursor routing.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant NVDA
    participant UIA
    participant BrailleDevice

    User->>NVDA: Perform action (e.g., typing)
    NVDA->>UIA: Detect caret movement using events
    UIA-->>NVDA: Return caret position
    NVDA->>BrailleDevice: Update braille output with caret position
Loading

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

Outside diff range, codebase verification and nitpick comments (1)
source/NVDAObjects/UIA/winConsoleUIA.py (1)

Line range hint 284-307: Consider adding more detailed logging for UIA notifications.

While the current logging warns about blocked notifications, additional logs could provide more context about the notifications being processed. This can be helpful for debugging and understanding the flow of events.

log.debug(f"Processing UIA notification: {kwargs}")

user_docs/en/changes.md Outdated Show resolved Hide resolved
@AppVeyorBot
Copy link

See test results for failed build of commit d44d6587a6

@LeonarddeR LeonarddeR added this to the 2024.4 milestone Aug 24, 2024
@AppVeyorBot
Copy link

See test results for failed build of commit d44d6587a6

@seanbudd seanbudd added the conceptApproved Similar 'triaged' for issues, PR accepted in theory, implementation needs review. label Aug 27, 2024
@seanbudd
Copy link
Member

Could you please use the revert template in future? https://github.com/nvaccess/nvda/blob/master/.github/PULL_REQUEST_TEMPLATE/revert.md

@seanbudd seanbudd changed the base branch from master to beta August 27, 2024 03:13
@seanbudd seanbudd merged commit 9d95367 into nvaccess:beta Aug 27, 2024
1 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
conceptApproved Similar 'triaged' for issues, PR accepted in theory, implementation needs review.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants