Support bound Flyout opened and closed events - #368
Merged
Merged
Conversation
This was referenced Aug 21, 2026
This was referenced Aug 28, 2026
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
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
EventTriggerBehaviorobserveFlyout.OpenedandFlyout.Closedthrough strongly typed subscriptionsRoot cause
Avalonia 12's
FlyoutBasederives fromAvaloniaObject, notStyledElement. A behavior attached directly to a Flyout could register the requested CLR event through the reflection fallback, but it had no logical parent or inherited data context. Consequently,InvokeCommandAction.Command="{Binding ...}"remained unresolved and made the event appear not to fire.The generic reflection path was also unnecessary for the two known Flyout lifecycle events.
Changes
OpenedandClosedinAddEventHandlerRegistrythrough a focusedFlyoutEventHandlerFlyoutBase.TargetPropertyTests
A compiled-XAML headless fixture matches the reported pattern:
FlyoutOpenedandClosedeach invoke a compiled-bound command exactly oncePassEventArgsToCommandreceives the original event argumentValidation
EventTriggerBehaviorTests: 5 passedXaml.Behaviors.Interactivity.UnitTests: 93 passedXaml.Behaviors.Interactions.UnitTests: 90 passed, 2 pre-existing skippedgit diff --check: cleanCloses #350