Skip to content

fix: Avoid unnecessary repeated checks for text changes #432

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

Merged
merged 1 commit into from
Jun 15, 2024

Conversation

mwcampbell
Copy link
Contributor

This is necessary if a large number of nodes have changed in a large document, but the text itself hasn't changed. That currently happens when scrolling GtkTextView, and while I could probably optimize that specific case somehow, this optimization is easier and, as far as I can tell, doesn't break anything.

Copy link
Member

@DataTriny DataTriny left a comment

Choose a reason for hiding this comment

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

I can't think of any downside to this optimization either. The only early return happens when the text is unchanged.

@DataTriny DataTriny merged commit 0e89671 into main Jun 15, 2024
10 checks passed
@DataTriny DataTriny deleted the atspi-repeated-text-change-checks branch June 15, 2024 13:02
@mwcampbell mwcampbell mentioned this pull request Jun 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants