This repository has been archived by the owner on Jun 16, 2024. It is now read-only.
fix: Use optional chaining to fix error when windowId is undefined in Wayland #490
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.
Summary
On KWin Wayland (5.27.6), I noticed that bismuth is throwing the ff. error when tiling Firefox causing tiling to break so I investigated and was able to pinpoint the error. It turns out windowId is undefined for some apps so I changed it to optional chaining which fixed the problems I've been having with tiling.
Here's how it worked before this change (the other windows don't resize immediately, eventually they stop tiling altogether):
bismuth-broken.mp4
Here's how it worked after this change (the other windows resize immediately):
bismuth-working.mp4
Breaking Changes
Should not break anything.
UI Changes
None
Test Plan
a. The remaining windows should resize correctly
b. Previously, these windows don't resize as one of the handlers throws the above error and fails to process the event
Related Issues
Potentially closes #473 or at least fixes one problem related to wayland.