event-routing

In the MSDN article Understanding Routed Events and Commands In WPF , it states an event will bubble (propagate) up the visual tree from the source element until either it has been handled or it reaches the root element. However, in this example, when you click the button, it doesn't "bubble up the visual tree" to get handled by the parent StackPanel event , i.e. clicking on the button fires no event. Why not? What do they mean then by "bubbling up" if not this? XAML: <Window x:Class="TestClickEvents456.Window1" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http:/

I realised that when using an InvokeCommandAcction associated to an EventTrigger, the original event was still routing up to the parent elements until it is handled. Well, I guess it is an expected behavior. But my question is how I can mark the event as Handled so it does not propagate up through the whole UI tree? Actually, as you handle this event in a command, everything will be handled in this command, therefore it does not need to propagate. And in one corner case I found, it causes some unwanted behavior. For example, I open a new window when a user double click an element