WPF MVVM中，UserControl设置e.Handled=true后双击事件仍冒泡至父控件？

Let's break down why this is happening and walk through actionable fixes.

Root Causes #

You’re hitting two key quirks with WPF routing events and the Interactivity library:

1. Interactivity Triggers Ignore Handled by Default
   The i:EventTrigger from System.Windows.Interactivity doesn’t respect the Handled flag out of the box. Internally, it uses AddHandler with handledEventsToo: true, meaning it will respond to events even if they’ve been marked as handled by child controls.

2. TextBox's MouseDoubleClick is a Synthetic Event
   The MouseDoubleClick event on TextBox isn’t a raw input event—it’s built from underlying MouseDown/MouseUp events. Even if you mark the MouseDoubleClick as handled, the raw mouse events might still bubble up to the ListView, triggering its double-click event.

Fixes You Can Implement #

Fix 1: Tell the ListView's Trigger to Respect Handled Events #

Modify the EventTrigger on your ListView to set HandledEventsToo="False". This makes it only respond to events that haven’t been marked as handled:

<ListView>
  <i:Interaction.Triggers>
    <i:EventTrigger EventName="MouseDoubleClick" HandledEventsToo="False">
      <i:InvokeCommandAction Command="{Binding DoubleClickCommand}" CommandParameter="{Binding data}" />
    </i:EventTrigger>
  </i:Interaction.Triggers>
  <!-- Your ListView content here -->
</ListView>

Fix 2: Use the Preview (Tunnel) Event Instead #

Tunnel events (prefixed with Preview) fire before bubble events. If you handle PreviewMouseDoubleClick on the TextBox and mark it as handled, it stops the event from ever reaching the bubble phase (and thus the ListView):

First, update your TextBox's event binding in XAML:

<TextBox PreviewMouseDoubleClick="textbox_PreviewMouseDoubleClick" />

Then update your code-behind:

private void textbox_PreviewMouseDoubleClick(object sender, MouseButtonEventArgs e)
{
    e.Handled = true;
}

This is the most reliable approach for stopping event propagation.

Fix 3: Bind a Command Directly to the TextBox (MVVM-Friendly) #

Since you’re using MVVM, ditching the code-behind event handler entirely is a cleaner approach. Bind a command directly to the TextBox's double-click event, and handle the logic in your ViewModel:

<TextBox>
  <i:Interaction.Triggers>
    <i:EventTrigger EventName="MouseDoubleClick">
      <i:InvokeCommandAction Command="{Binding TextBoxDoubleClickCommand}" />
    </i:EventTrigger>
  </i:Interaction.Triggers>
</TextBox>

In your ViewModel, implement TextBoxDoubleClickCommand to handle the TextBox-specific logic. If you need to prevent the ListView's command from firing, add a flag in your ViewModel that the ListView's command checks before executing.

Fix 4: Hacky Workaround (Not Recommended) #

If you must stick with the MouseDoubleClick event in code-behind, you can manually mark the underlying MouseDown event as handled to stop propagation:

private void textbox_MouseDoubleClick(object sender, MouseButtonEventArgs e)
{
    e.Handled = true;
    // Mark the associated MouseDown event as handled to block bubbling
    var mouseDownEvent = Mouse.MouseDownEvent;
    (sender as UIElement)?.RaiseEvent(new MouseButtonEventArgs(e.MouseDevice, e.Timestamp, e.ChangedButton)
    {
        RoutedEvent = mouseDownEvent,
        Handled = true
    });
}

This relies on internal event mechanics, so use it only as a last resort.

内容的提问来源于stack exchange，提问作者Jayakrishnan