Backport fix NullReferenceException in X11Window.Activate #14787
Conversation
This file contains 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
kekekeks
approved these changes
Mar 2, 2024
grokys
added
bug
backported-11.0.x
backport-candidate-11.1.x
maxkatz6
removed
the
backport-candidate-11.1.x
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.
What does the pull request do?
In v11.0.9 the
X11Window.Activatemethod throws theNullReferenceExceptionwhenplatform.Options.EnableInputFocusProxy == falseandx11.Atoms._NET_ACTIVE_WINDOW == IntPtr.Zero.The issue is fixed in the master branch:
Avalonia/src/Avalonia.X11/X11Window.cs
Line 1143 in aeafbf9
This PR backports the fix to v11.0.x