Revert "[fix] Frameless floating windows: resize, state persistence, geometry (#2008)"#2042
Merged
ten9876 merged 1 commit intoApr 26, 2026
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Reverts #2008.
The frameless-window changes regressed input handling in the Aetherial Audio container — multiple applets (knobs, chain-tile drag-to-reorder, etc.) stopped responding correctly to mouse events after the merge. Likely cause is the new
FramelessResizerrecursively installing its event filter on every descendant widget and capturing events that inner controls needed.Backing out so we can investigate and ideally re-land the four fixes in smaller, isolated PRs:
FramelessResizer— needs scope tightened (event filter on the window only, not all children) before re-landingOriginal PR by @chibondking — see #2008 for the breakdown.