The KeyUp event is a bubbling event. This means that if multiple KeyUp event handlers are registered for a sequence of objects connected by parent-child relationships in the object tree, the event is received by each object in that relationship. The bubbling metaphor indicates that the event starts at the object that has focus while the key is pressed and works its way up the object tree. For a bubbling event, the sender available to the event handler identifies the object where the event is handled, not necessarily the object that actually received the input condition that initiated the event. To get the object that initiated the event, use the OriginalSource value of the event's RoutedEventArgs event data.

Note:

Handling keyboard events might vary between browsers. When you create an application that uses keyboard input, make sure to test the application in your target browsers.

Element focus and the ability to initiate a keyboard event are tied. In order to generate the KeyUp event, the UIElement must have focus.

On the TextBox class, there is a TextChanged event that has potential interactions with KeyUp, as well as special handling for keys such as ENTER. For details, see TextBox.

KeyUp and OnKeyUp

Controls that inherit KeyUp can provide handling for the event that acts as handler for all instances, by overriding the OnKeyUp method. This might include marking the Handled value of the event as true, which has the effect of suppressing further handling of the KeyUp event for some or all keys on any instance of the control (and potentially any subclass of the control). For instance, ButtonBase implements OnKeyUp in such a way that the SPACE key invokes a button click, but also sets Handled, which prevents SPACE from being reported as a KeyUp event that could be handled by a button instance. For more information, see OnKeyUp.

You can also register handlers such that they are invoked even for already-handled routed events. For more information, see AddHandler.