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 ...

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...